← ClaudeAtlas

stage-reviewlisted

Reviews a completed pipeline stage before advancing to the next one. Verifies all declared outputs exist, runs the stage's Review Checkpoint criteria, checks quality against the Process intent, and confirms downstream readiness. Use when: reviewing stage output, checking if ready to advance, verifying stage completion.
mcmespinaa/folder-structure-protocol · ★ 3 · Code & Development · score 66
Install: claude install-skill mcmespinaa/folder-structure-protocol
# Stage Review Skill Reviews a completed pipeline stage to determine whether it's safe to advance. Checks output existence, runs checkpoint criteria, and verifies the next stage's inputs are satisfied. ## Trigger Use this skill when: - The user asks to review a stage before moving on ("review stage 2", "can I advance?", "check stage output") - The user says "stage review", "stage checkpoint", "is this stage done?" - The user wants a quality gate between `/run-stage` and the next stage - The user is unsure whether a stage's output is good enough ## Procedure ### Step 1: Identify Target Stage Determine which stage to review: - If the user specifies a stage number or name, use that - If the user says "review this stage" or "can I advance?", find the most recent stage with output files - If ambiguous, list stages that have output and ask ```bash # Find stages with output for dir in [0-9][0-9]_*/; do if [ -d "$dir/output" ] && [ "$(ls -A "$dir/output" 2>/dev/null)" ]; then echo "$dir — has output" else echo "$dir — no output yet" fi done ``` ### Step 2: Read the Stage Contract Load `{stage-folder}/CONTEXT.md`. Extract: - **Outputs table** — what files should exist and where - **Review Checkpoint** — the criteria the human (and this skill) should verify - **Process section** — what the stage was supposed to do (for quality assessment) - **Inputs table** — what the stage had to work with (for traceability) If the stage has no CONTEXT.md, report: "Stage {NN} h