update convert to phased and phase authoring
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
# Phase {{NN}} — {{Short Title}}
|
||||
|
||||
**Feature:** `{{.agent/workflows/<name>.md | .agent/features/<name>.md | .agent/user_stories/<name>.md | "n/a"}}`
|
||||
**Context:** `{{PLAN.md sections / files this phase builds on}}`
|
||||
|
||||
## Objective
|
||||
{{1–3 sentences: what this phase delivers (the delta from current state to the contract)}}
|
||||
|
||||
## Dependencies
|
||||
- `{{NN_name}}` ({{complete|todo}}) — {{what is needed from it}}
|
||||
{{or "— (none)"}}
|
||||
|
||||
## Tasks
|
||||
1. `{{path/to/file}}` — {{specific change, file-level detail}}
|
||||
2. `{{path/to/file}}` — {{specific change}}
|
||||
|
||||
## Testing & Quality
|
||||
- Unit/integration: {{tests required for all new/modified logic — name the behaviors to cover}}
|
||||
- Coverage: **>90%** on new/modified code
|
||||
{{project additions, e.g. the CLI Contract Execution Phase / Capability Execution Phase / Playwright Execution Phase block}}
|
||||
|
||||
## Completion Criteria
|
||||
- [ ] {{observable check: command to run / endpoint to hit / artifact to exist}}
|
||||
- [ ] test suite green, coverage >90%
|
||||
- [ ] no behavior change in completed phases
|
||||
{{project additions, e.g. a commit command per AGENTS.md conventions}}
|
||||
@@ -0,0 +1,34 @@
|
||||
# {{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` | {{...}} |
|
||||
Reference in New Issue
Block a user