docs(plan): MVP implementation plan and Design & Contracts prompt #2
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/planning"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Completes the Planning stage of the AI-PDLC: full decomposition of the MVP
into epics and agent-executable tasks, plus the system prompt for the next
stage (Design & Contracts).
Changes
Plan (
docs/plan/) — newroadmap.md— 7 epics (E1…E7), Mermaid dependency graph, critical path(E1 → E2 → E3 → E7), blocker registry, Design/Contracts readiness audit
e1-infrastructure.md…e7-pilot.md— 57 tasks (TASK-1…57), each with:dependencies, traceability to FR/RULE/D-n, scope boundaries, and testable
DoD derived from spec acceptance criteria
Specification (point updates, per spec process)
(
OPEN_QUESTIONS.md)flake.nix(uv2nixworking-devshells+ Node.js from nixpkgs) —registry.md,constraints.mdCHANGELOG.mdentry (2026-08-08)Prompts (
docs/prompts/)design-contracts-agent.md— CO-STAR system prompt for the Lead ContractDesigner (event JSON Schemas, package interfaces, DDL, OpenAPI contracts)
Verification
covered by tasks; gaps found during the audit were fixed (TASK-26 night
rules, TASK-56 Docker images, TASK-57 prompt templates)
affected tasks are marked, none hidden
D-104/OPEN-11 additions
Next stage
Design & Contracts (agent prompt included): produces machine-readable
contracts — event JSON Schemas (closes OPEN-11 via owner approval),
packages/domain/packages/configinterfaces, DB DDL, OpenAPI forviewer/admin API.