| name | prep-section |
| description | Analyze a roadmap Phase for dependencies and implementation order. Use when user says "prep section", "prepare phase", "analyze phase dependencies", or wants to plan implementation order for a Phase. Creates visual workflow and saves to file. |
Prep Section
Analyzes a roadmap Phase to determine optimal implementation order.
Workflow
Step 1: Extract Phase
Identify the Phase from user's request.
If clearly specified: Extract directly (e.g., "prep Phase 7")
If ambiguous or missing: Prompt:
"Which Phase would you like to prepare? (e.g., 'Phase 7: My Library & Discovery')"
Step 2: Read Roadmap
ai_docs/prep/roadmap.md
Locate the specified Phase and extract all subsections.
Step 3: Dependency Analysis
For each subsection, identify:
- Prerequisites: Which subsections must complete first
- Database dependencies: Schema/migrations that block other work
- Component dependencies: Shared components needed by multiple subsections
- API dependencies: Server actions or queries needed by UI work
Step 4: Priority Assessment
Rank subsections by:
- Critical path: Subsections that block the most other work
- Risk level: Complex subsections that may surface issues early
- Value delivery: User-facing features vs internal infrastructure
Step 5: Present Visual Workflow
Output a workflow diagram showing implementation order:
## Phase X Implementation Workflow
### Sequential Order
1. [Subsection A] - Database schema (blocks all)
2. [Subsection B] - Core queries (blocks C, D)
3. [Subsection C] - UI Component
4. [Subsection D] - Server Actions
5. [Subsection E] - Feature page
6. [Subsection F] - Integration/polish
Include notes on:
- Estimated complexity per subsection (Low/Medium/High)
- Why this ordering (what blocks what)
- Potential risk areas
Step 6: Save Workflow to File
Save the workflow analysis to:
ai_docs/scratch/Phase{N}-workflow.md
File naming examples:
ai_docs/scratch/Phase7-workflow.md
ai_docs/scratch/Phase6B-workflow.md
ai_docs/scratch/Phase13-workflow.md
File contents: Include the complete workflow diagram with:
- Sequential implementation order
- Complexity estimates
- Dependency explanations
- Risk areas
Create the ai_docs/scratch/ directory if it doesn't exist.
Confirm save:
"Workflow saved to ai_docs/scratch/Phase{N}-workflow.md"
Example Usage
User: "prep Phase 7"
Response:
- Read roadmap, find Phase 7: My Library & Discovery
- Extract subsections: My Library Page, Shared with Me, Certified Prompts, Tags & Stars schema, Tags & Stars actions
- Analyze: Database schema blocks UI pages
- Present workflow:
-
- Tags & Stars schema (High - blocks all)
-
- Tags & Stars actions (Medium - blocks UI)
-
- My Library Page (Medium)
-
- Shared with Me (Medium)
-
- Certified Prompts Page (Low)
- Save to
ai_docs/scratch/Phase7-workflow.md
Key Principles
- Dependencies first: Always surface blocking relationships
- Clear ordering: Present subsections in implementation sequence
- Complexity visibility: Show effort estimates for planning
- Persist to file: Save workflow to
ai_docs/scratch/ for reference