Skills

Review Work

Quality gate: verify each acceptance criterion of a completed task/work unit, run...

Install

npx skills add hashgraph-online/awesome-codex-plugins --skill review-work -g -a claude-code -y
Category
Engineering
Updated
3d ago
License
Apache-2.0
Context cost
Lightabout 1,472 tokens
Runs scripts
No, instructions only

What it does

Quality gate: verify each acceptance criterion of a completed task/work unit, run quality checks, and create follow-up tasks for gaps. Use before merging or to audit delivered work. Invoked as /agiflow:review-work <work-unit-or-task>. Uses get_work_unit, get_task, update_task, create_task, create_task_comment.

Invoked as /agiflow:review-work. In hosts without slash-prompts, this skill is triggered by matching intent and drives AgiFlow via its MCP tools.

Usage:

  • /agiflow:review-work <work-unit-slug-or-id> - Review a specific work unit
  • /agiflow:review-work <task-slug-or-id> - Review a specific task
  • /agiflow:review-work - List completed items for review

Examples:

  • /agiflow:review-work DXX-WU-1 (review work unit by slug)
  • /agiflow:review-work DXX-3 (review task by slug)
  • /agiflow:review-work (interactive selection)

Purpose Verify that completed work actually meets its acceptance criteria, catches quality issues, and is ready to ship. AI code has 1.7x more defects than human-written code, review is the last line of defense before shipping.

Guardrails

  • Review what exists, do not implement fixes during review (create follow-up tasks instead).
  • Every acceptance criterion gets a pass/fail verdict with evidence.
  • Flag issues by severity: blocker (must fix), warning (should fix), note (nice to fix).
  • Be honest, a "pass" with gaps is worse than a clear "needs rework".

If a work unit or task slug/id is provided, load it with get_work_unit / get_task; otherwise list candidates with list_work_units / list_tasks for selection.


AgiFlow Project Management Guidelines

Follow the shared AgiFlow project-management guidelines in references/agiflow-agents.md, agent assignment, the task status workflow and transitions, work-unit best practices, and the tags strategy apply to this workflow.


Steps

1. Load the Work for Review

If work unit slug/id provided:

  1. Use get_work_unit MCP tool to load the work unit and its tasks.
  2. For each task in the work unit, use get_task to load full details (acceptance criteria, devInfo, comments).

If task slug/id provided: 3. Use get_task MCP tool to load the task with full details.

Read the whole SKILL.md on GitHub

More in Engineering