Scaffold Pipeline Reference

This skill provides context about the scaffold prompt pipeline ordering. When the user asks about which command to run next, what order to follow, or how the pipeline works, use this reference.

Pipeline Order

Standalone Commands

Key Dependencies

PRD → Tech Stack → Coding Standards → TDD Standards → Project Structure
                                                            ↓
PRD → User Stories → Implementation Plan → Execution
                                    ↓
Dev Setup → Git Workflow → Claude.md Optimization → Workflow Audit
                                                            ↓
                                              Implementation Plan Review

Critical Ordering Constraints

1. •Beads Setup before everything else in Phase 2 — creates CLAUDE.md
2. •Tech Stack before Permissions, Coding Standards, and TDD — they reference it
3. •Dev Setup before Git Workflow — Git Workflow references lint/test commands
4. •Claude.md Optimization before Workflow Audit — optimize first, verify second
5. •Implementation Plan before Implementation Plan Review — can't review what doesn't exist

Completion Detection

When checking pipeline status, use these detection criteria:

Detection rules:

• •If the file exists → step was likely run (even without tracking comment — older projects lack them)
• •If the tracking comment exists in the file → step was definitively run
• •For update-only steps (2, 15, 16, 17, 18, 20): file existence alone only confirms the prerequisite ran; check for the specific tracking comment to confirm the update step itself