plan

# Create an Implementation Plan Translate requirements and system designs into a delivery plan under `docs/plans/<initiative>/`. The plan and its work-order files are implementation records. They are not product specifications. Read `docs/specs/guide/plans-and-work-orders.md` and `docs/specs/guide/traceability-and-lifecycle.md` before you write the plan. ## Inputs Read these sources in full: - The applicable requirement documents and `REQ-*` or `AC-*` IDs. - The applicable system-design documents. - Related ADRs. - The relevant source, tests, and one similar implementation. Use the legacy feature specification during migration only when no replacement requirement or design exists. Read each spec's `Implementation Plans` and related-plan links, then inventory all existing companion plan directories. Treat linked packages as one synchronized implementation record: reconcile every affected task scope, E2E scenario matrix, status, and exact final verification results/counts before completion. ## Outputs Create: ```text docs/plans/<initiative>/plan.md docs/plans/<initiative>/task-<NN>-<short-slug>.md ``` `plan.md` is the work-package manifest. Each `task-*.md` file is one work order. ## Workflow ### 1. Map the change Run the `/interview-me` assumption check, reusing settled specification choices. Resolve material blockers before decomposing the affected work. For large uncertain initiatives, use that skill's decision-mapping reference first. Identify: - The require...