An executable AI development workflow focused on reliable engineering rather than conversational memory.
AGENTS.md defines policy. skills/workflow/scripts/workflow.ps1 enforces phase
transitions and stores committable state in .progress/workflow.json, allowing a
workflow to resume on another machine. Before integration, remove-progress
removes that state from every feature-branch commit.
For multi-increment, architectural, or public-interface work. The user shapes the design, approves each increment, reviews the branch, and explicitly approves integration.
flowchart TD
START --> DESIGN --> SPLIT --> BRANCH --> BUILD --> VERIFY --> COMMIT
COMMIT -->|more increments| BUILD
COMMIT -->|plan complete| SUMMARY --> MERGE_READY --> MERGE
Runs the same phases, reviews, tests, commits, and integration preparation as Detailed. The agent handles intermediate decisions; the user is involved once at the final summary, whose approval authorizes integration.
flowchart TD
START --> DESIGN --> SPLIT --> BRANCH --> BUILD --> VERIFY --> COMMIT
COMMIT -->|more increments| BUILD
COMMIT -->|plan complete| SUMMARY --> FINAL_REVIEW --> MERGE
For one small, self-contained change with a handful of clear design choices. It uses one build/verify/commit pass on the current branch.
flowchart TD
START --> DESIGN --> BUILD --> VERIFY --> COMMIT
Future Detailed increments can be inserted or reordered without changing active or completed increment identity. The controller validates approvals, branches, commits, and legal transitions before saving state atomically. Every controller change prints user-presentable Markdown tables for the workflow phases and increment statuses.
AGENTS.md— concise policy and entry pointagents/— phase role definitionscode-review/— ignored local review JSON and generated Markdownskills/workflow/— executable workflow state machineskills/install-powershell/— PowerShell 7 bootstrap instructionsskills/— review, design, ADR, debug, summary, progress cleanup, integration, and retrospective actions