phase-review
Skill9 starsChanged 3 months agoMITView on GitHub
Phase transition review — walkthrough built features, validate assumptions, refresh research, decide direction, and plan next phase.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tripinfinite-gif/claude-skill-phase-reviewtheir own version, first seen May 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tripinfinite-gif/claude-skill-phase-review★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- help-meSkill
- ideateSkill
- lanesSkill
- manual-testSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- pr-statusSkill
- quality-checkSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- retrospectiveSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- uninstallSkill
- weekly-maintenanceSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 8 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Read these files (skip any that don't exist with a warning):
- Very specific: line 45
Read epic files from docs/reference/backlog/ to determine:
- Very specific: line 70
PIVOT: Run /discover Phases 1-3 with new direction Save to vision/phase-N+1-discovery.md.
- Very specific: line 83
Update docs/reference/BACKLOG_INDEX.md with new epics
- Very specific: line 84
Create new epic files in docs/reference/backlog/
- Very specific: line 85
Update docs/progress.md with phase review outcomes
- Very specific: line 86
Update docs/reference/DECISION_LOG.md with any revised decisions
- Very specific: line 100
Read scale from vision/classification.md:
- Distinctive: line 101
Quick Build: Run only E0N-001 + E0N-004 + E0N-006 (3 stories)
- Distinctive: line 102
Standard: Run all 6 stories
- Distinctive: line 103
Platform: Run all 6 + Architecture Review (E0N-007)
- Distinctive: line 104
Pioneering (post-spike): Run E0N-001 + E0N-004 + full /discover re-entry
- Distinctive: line 108
NEVER skip the user walkthrough (E0N-001) — this is the core value of phase review
- Distinctive: line 109
NEVER auto-decide PIVOT vs PERSEVERE — this is always a user decision
- Distinctive: line 110
ALWAYS include Phase Transition stories in the next phase backlog
- Very specific: line 111
ALWAYS update ASSUMPTION_REGISTER and DECISION_LOG with review outcomes
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
phase-review
Running Phase Transition Review for phase: $ARGUMENTS
Process Flow
START → Load context (ASSUMPTION_REGISTER, DECISION_LOG, BACKLOG_INDEX, progress.md)
→ Identify completed epics
→ Walk through Phase Transition Stories (E0N-001 → E0N-006) interactively
→ Generate outputs to docs/reviews/ and vision/
→ If user approves next phase: invoke /ideate with new vision
→ DONE1. Load Context
Read these files (skip any that don't exist with a warning):
docs/reference/ASSUMPTION_REGISTER.md— assumptions to validatedocs/reference/DECISION_LOG.md— decisions to reviewdocs/reference/BACKLOG_INDEX.md— epic completion statusdocs/progress.md— sprint history and metricsvision/project-pitch.md— original vision and No-Gosvision/classification.md— archetype and scale
Determine which phase we're reviewing from $ARGUMENTS or by counting completed review epics.
2. Identify Completed Work
Read epic files from docs/reference/backlog/ to determine:
- Which epics are complete (all stories done)?
- Which stories were carried over?
- What was the overall delivery rate?
3. Execute Phase Transition Stories
Walk through each story interactively. Read .claude/skills/discover/references/phase-transition-template.md for the full story definitions.
3A. Feature Walkthrough (E0N-001)
Walk through every built feature with the user. Copy template from .claude/skills/discover/assets/phase-walkthrough.md to docs/reviews/phase-N-walkthrough.md and fill it in.
3B. Assumption Validation (E0N-002)
Go through ASSUMPTION_REGISTER.md. For each HIGH-impact assumption: VALIDATED, INVALIDATED, or STILL UNKNOWN? Update the register.
3C. Research Refresh (E0N-003)
Load archetype from vision/classification.md. Run archetype-specific research from .claude/skills/discover/references/research-protocols.md (RC6 checkpoint). Save to docs/research/phase-N-refresh.md.
3D. Pivot or Persevere (E0N-004)
Load success criteria from .claude/skills/discover/references/engineering-by-archetype.md. Present current status vs targets. Apply decision framework (SCALE / PERSEVERE / PIVOT / KILL). Save to docs/reviews/phase-N-direction.md.
3E. Next Phase Elicitation (E0N-005)
Based on direction from 3D:
- SCALE: Elicit growth features and optimization targets
- PERSEVERE: Identify validation experiments for remaining unknowns
- PIVOT: Run /discover Phases 1-3 with new direction
Save to
vision/phase-N+1-discovery.md.
3F. Next Phase Backlog (E0N-006)
Generate next batch of epics from the phase N+1 discovery. The last epic is AGAIN a Phase Transition epic — maintaining the infinite cycle.
<HARD-GATE>
User approves the next-phase backlog before writing to files.
</HARD-GATE>4. Generate Outputs
After user approval:
- Update
docs/reference/BACKLOG_INDEX.mdwith new epics - Create new epic files in
docs/reference/backlog/ - Update
docs/progress.mdwith phase review outcomes - Update
docs/reference/DECISION_LOG.mdwith any revised decisions
Graceful Degradation
| Dependency | If Missing |
| ASSUMPTION_REGISTER.md | Skip assumption validation (E0N-002), note gap |
| DECISION_LOG.md | Skip decision review, note gap |
| vision/classification.md | Ask user for archetype during research refresh |
| WebSearch | Skip research refresh (E0N-003), note "no internet" |
| progress.md | Skip metrics comparison in pivot-or-persevere |
Scale Adaptations
Read scale from vision/classification.md:
- Quick Build: Run only E0N-001 + E0N-004 + E0N-006 (3 stories)
- Standard: Run all 6 stories
- Platform: Run all 6 + Architecture Review (E0N-007)
- Pioneering (post-spike): Run E0N-001 + E0N-004 + full /discover re-entry
Rules
- NEVER skip the user walkthrough (E0N-001) — this is the core value of phase review
- NEVER auto-decide PIVOT vs PERSEVERE — this is always a user decision
- ALWAYS include Phase Transition stories in the next phase backlog
- ALWAYS update ASSUMPTION_REGISTER and DECISION_LOG with review outcomes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

