--- description: "Task list template for feature implementation" --- # Tasks: [FEATURE NAME] **Input**: Design documents from `/specs/[###-feature-name]/` **Prerequisites**: plan.md (required), spec.md (required), research.md, data-model.md, contracts/ **Validation**: Validation tasks are NOT optional in this repository. Every document change task set MUST include the applicable validation and ledger-sync tasks. **Organization**: Tasks are grouped by user story so each document-maintenance slice can be completed, reviewed, and validated independently. ## Format: `[ID] [P?] [Story] Description` - **[P]**: Can run in parallel (different files, no dependencies) - **[Story]**: Which user story this task belongs to (e.g., US1, US2, US3) - Include exact file paths in descriptions ## Path Conventions - Main documents: `docs/design/01_Overview/`, `docs/design/02_Detailed_Design/`, `docs/design/03_Technical_Design/` - Governance documents: `docs/design/00_Management/` - Archive references: `docs/design/04_Appendix/Archive/` - Runtime guidance: `README.md`, `AGENTS.md`, `.specify/templates/` ## Phase 1: Scope & Source Confirmation (Shared Foundation) **Purpose**: Confirm the source-of-truth set and impact boundary before editing. - [ ] T001 Confirm target documents and exact chapters from spec.md - [ ] T002 Confirm governing source-of-truth documents and allowed references - [ ] T003 [P] Record scope judgment (in scope / needs confirmation / out of scope) - [ ] T004 [P] Identify cross-document impacts: terminology, numbering, diagrams, links, ledger updates --- ## Phase 2: User Story 1 - [Title] (Priority: P1) 🎯 MVP **Goal**: [Brief description of the first independently reviewable document update] **Independent Test**: [How to verify this story on its own] ### Implementation for User Story 1 - [ ] T005 [US1] Update target document in docs/design/... with the approved scope - [ ] T006 [US1] Sync affected anchors, references, numbering, or glossary terms in impacted docs - [ ] T007 [US1] Run `make validate-file FILE=` and capture result - [ ] T008 [US1] Run any required cross-document validation (`make check-links`, `make validate-mermaid`) and capture result - [ ] T009 [US1] Update `docs/design/00_Management/01_Project_Progress.md` if the change is important - [ ] T010 [US1] Update `docs/design/00_Management/03_Task_Checklist.md` if a tracked task is completed or materially changed **Checkpoint**: User Story 1 is reviewable, validated, and ledger-synced independently --- ## Phase 3: User Story 2 - [Title] (Priority: P2) **Goal**: [Brief description of the second independently reviewable update] **Independent Test**: [How to verify this story on its own] ### Implementation for User Story 2 - [ ] T011 [US2] Update target document in docs/design/... with approved changes - [ ] T012 [US2] Sync affected references, diagrams, or traceability entries - [ ] T013 [US2] Run `make validate-file FILE=` and capture result - [ ] T014 [US2] Run any additional required validation and capture result - [ ] T015 [US2] Update relevant management ledgers if applicable **Checkpoint**: User Story 2 is reviewable and validated independently --- ## Phase 4: User Story 3 - [Title] (Priority: P3) **Goal**: [Brief description of the third independently reviewable update] **Independent Test**: [How to verify this story on its own] ### Implementation for User Story 3 - [ ] T016 [US3] Update target document in docs/design/... with approved changes - [ ] T017 [US3] Sync affected supporting documents or guidance files - [ ] T018 [US3] Run `make validate-file FILE=` and capture result - [ ] T019 [US3] Run any additional required validation and capture result - [ ] T020 [US3] Update relevant management ledgers if applicable **Checkpoint**: All planned document updates are independently reviewable and validated --- ## Final Phase: Cross-Cutting Closure **Purpose**: Ensure repository-wide consistency after all story slices are complete. - [ ] T021 [P] Re-check source-of-truth alignment across all modified files - [ ] T022 [P] Re-check relative links, stable anchors, and Mermaid consistency across all modified files - [ ] T023 Prepare final summary with modified files, validation results, remaining risks, and next-step suggestions --- ## Dependencies & Execution Order ### Phase Dependencies - **Scope & Source Confirmation**: No dependencies; MUST finish before content edits - **User Stories**: Depend on confirmed scope and sources - **Final Phase**: Depends on all selected user stories being complete ### Within Each User Story - Update target document before syncing impacted documents - Complete content edits before validation - Complete validation before ledger updates are marked done - Complete ledger sync before final summary ### Parallel Opportunities - Scope analysis tasks marked [P] can run in parallel - Different impacted supporting files can be updated in parallel if they do not touch the same file - Validation tasks for different files can run in parallel when commands are independent --- ## Notes - Every task set MUST preserve the single-source-of-truth model - Archive is for verification and traceability, not direct formal output replacement - Do not omit validation or ledger tasks when they apply - Avoid vague tasks; every task should name the file path and expected outcome