Section Splitting

# Section File Writing Write individual section files from the plan using **parallel subagents** for efficiency. This step assumes `sections/index.md` already exists. ## Input Files - `/claude-plan.md` - implementation details - `/sections/index.md` - section definitions and dependencies ## Output ``` /sections/ ├── index.md (already exists) ├── section-01-.md ├── section-02-.md └── ... ``` ## Parallel Execution Strategy **Launch one subagent per section in a single message** for maximum parallelization: ``` ┌─────────────────────────────────────────────────────┐ │ PARALLEL SUBAGENT APPROACH │ │ │ │ 1. Parse index.md to get SECTION_MANIFEST list │ │ 2. Check which sections already exist │ │ 3. Launch ALL missing sections as parallel Tasks: │ │ │ │ Task(prompt="Write section-01-...") │ │ Task(prompt="Write section-02-...") │ │ Task(prompt="Write section-03-...") │ │ ... (all in ONE message) │ │ │ │ 4. Wait for all subagents to complete │ │ │ └─────────────────────────────────────────────────────┘ ``` ### Parse SECTION_MANIFEST Extract section list from index.md: ```markdown ``` ### Launch Parallel Tasks For each section in the manifest, include a Task in a single message: ```python Task( subagent_type="general-purpose", prompt=""" Write section file: section-01-foundation Inputs: - /claude-plan.md - /sections/index.md Output: /sections/section-01-foundation.md Requirements: [see Section File Template below] """ ) Task( subagent_type="general-purpose", prompt="Write section file: section-02-config ..." ) # ... one Task per section ``` **Why parallel?** Each section is independent - they all read from the same source files (`claude-plan.md`, `index.md`) but write to different output files. ### Resume Handling If some sections already exist: 1. Only launch Tasks for MISSING sections 2. Skip sections that have corresponding `section-*.md` files ## Section File Requirements **CRITICAL: Each section file must be completely self-contained.** The implementer reading a section file should NOT need to reference `claude-plan.md` or any other document. They should be able to: 1. Read the single section file 2. Create a TODO list 3. Start implementing immediately Include all necessary background, requirements, and implementation details within each section. ### Section File Template ```markdown # Section NN: {Section Name} ## Background {Why this section exists, what problem it solves} ## Requirements {What must be true when this section is complete} ## Dependencies - Requires: {list of prior sections that must be complete} - Blocks: {list of sections that depend on this one} ## Implementation Details {Detailed implementation guidance} ### {Subsection 1} {Details} ### {Subsection 2} {Details} ## Acceptance Criteria - [ ] {Criterion 1} - [ ] {Criterion 2} - [ ] {Criterion 3} ## Files to Create/Modify - `path/to/file1.ts` - {description} - `path/to/file2.ts` - {description} ``` ## Completion All sections are complete when every section in the SECTION_MANIFEST has a corresponding `section-NN-name.md` file. After all parallel Tasks complete, update the main TODO list to mark section writing as done.