skills/convert-to-phased/assets/plan-template.md

{{Project Name}} — Master Plan

Master design document for a phased-execution project. The LOCKED DECISIONS below are binding: no phase may introduce technology outside them without explicit user permission.

Assumptions & Design Principles

• {{...}}

Architectural Anchors

COMPONENT	DECISION	RATIONALE	STATUS
{{component}}	{{decision — inherited from the existing codebase}}	{{why}}	LOCKED
{{component}}	{{decision awaiting ratification}}	{{why}}	PROPOSED

High-Level Architecture

{{Component breakdown and data flow, mirroring the actual code.}}

Data Model

{{Existing schemas, state transitions, and persistence details.}}

Validation / Verification Workflow

{{Multi-step logic ensuring high-confidence outputs (unit → integration → contract/E2E → coverage floor).}}

{{Domain Section}}

{{CLI/UX Strategy | Public API design principles | UI/UX guidelines (layout, accessibility, asset policy) — whichever matches the project's domain.}}

Phase Roadmap

#	Phase	Feature file	Objective (one line)
01	{{NN_name}}	—	foundation: adapt validate.sh, green test baseline
02	{{NN_name}}	.agent/{{workflows|features|user_stories}}/{{name}}.md	{{...}}