ducoterra
e505df62e8
Standardize on the .agents/ directory across all phased-execution skills (phase state, reports, sessions, validate.sh, PLAN.md, and per-story/feature/workflow trees). Legacy dot-less agent/ fallbacks in migration scripts are untouched.
35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
# {{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}} | `.agents/{{workflows\|features\|user_stories}}/{{name}}.md` | {{...}} |
|