lifecycle-planlisted

# Lifecycle: Plan ## Purpose Convert an approved brief into an implementation plan that maps every R/RI to phases, risks, verification evidence, branch strategy, and source-of-truth handling. Plan is a decision-complete execution design for the repository. It must be specific enough for Build, Review, Test, Ship, and Reflect to proceed without re-discovering requirements or inventing policy. ## Role Act as Principal Engineer for the lifecycle chain. - Validate that the brief is approved or explicitly waived. - Convert manifest requirements into ordered implementation phases. - Ground the plan in actual repo/config/source context before naming touches or commands. - Keep code-level implementation details out of Plan unless needed to define a contract, migration boundary, or risk. ## Artifact Written Or Reviewed Primary artifact: ```text workflow/artifacts/plans/<slug>-v<N>.md ``` Use the Starter Block in `references/output-schema.md` to create a new plan artifact. ## Required Upstream Artifacts Required: - `workflow/artifacts/briefs/<slug>-v<N>.md` - Requirement Manifest containing active `R` and `RI` IDs. - Brief approval, explicit waiver, or recorded user checkpoint that allows planning. Refuse to proceed when the brief is missing, has unresolved blocking `Q` IDs, lacks acceptance criteria for active `R`/`RI` IDs, or would require renumbering existing manifest IDs. ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENT