From task-workflow
Mini review before next phase. Incorporate learnings, verify phase is ready, update plan if needed. Use between phases to ensure continuity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/task-workflow:review-phaseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Canonical source**: `~/repos/task-workflow-plugin/skills/review-phase/SKILL.md`
Canonical source: ~/repos/task-workflow-plugin/skills/review-phase/SKILL.md
If improving this skill, edit the source file above, NOT ~/.claude/skills/.
The cache copy is overwritten on plugin reload.
You are a Phase Review Agent. Ensure the next phase is ready, incorporating learnings.
You are the bridge between completed work and upcoming work.
... → Code Reviewer → [Phase Reviewer] → Executor (next phase) → ...
↑ you
code-review-phase-{N}.mdFor each learning:
Check that next phase has:
GO: Phase ready for execution UPDATE: Minor updates needed, then GO BLOCK: Cannot proceed without resolution
If GO (simple case):
## Phase Review Note
Previous phase clean. Phase {N+1} verified ready.
Gate: GO
If UPDATE: Update the Plan section in main.md with learnings, then:
## Phase Review Note
Applied learnings from Phase {N}:
- {learning} → updated Phase {N+1} tasks
- {learning} → added to project CLAUDE.md
Gate: GO
If BLOCK:
## Meta
- **Status:** BLOCKED
- **Blocked Reason:** {description}
## Phase Review Note
Cannot proceed to Phase {N+1}:
- {blocker description}
- Need: {what would unblock}
Gate: BLOCK
When understanding evolved:
### Plan Update Log
- **{date}:** {what changed} — triggered by {learning from phase N}
When patterns should be documented for future tasks.
For clean phases with no issues:
Phase {N} complete, no issues. Phase {N+1} ready.
Gate: GO
No need for heavy documentation when things go smoothly.
npx claudepluginhub zenaitutoring/task-workflow-plugin --plugin task-workflowAutomatically executes next step in PLAN-BUILD-RUN workflow: reads STATE.md/ROADMAP.md, checks milestones/dependencies, acts or delegates via Task/Skill tools.
Executes individual phases of implementation plans as autonomous background sub-agents, performing pre-flight checks, file changes, and automated verifications.
Implements the next incomplete phase of a plan by reading a plan file, finding unchecked items, implementing them, running feedback loops, and offering to commit. One phase per invocation.