Structured workflow for AI-assisted development. Prevents chaos, maintains discipline.
For detailed context on the workflow system, validation evidence, and comparison to traditional artifacts, see What Is This Repo?
Exploration → Are we building the right thing?
- Question architecture, make decisions
- Output: What to build
Planning → How do we build it?
- Break into atomic tasks with TDD
- Output: Implementation roadmap
Implementation → Build it
- Test-first workflow, commit per phase
- Output: Working, tested code
For Humans:
- Create brief:
docs/workflow/brief-creation.md - Work with AI through modes
- Brief tracks progress
For AI:
- Read
docs/workflow/session-start.mdfirst - Follow mode-specific workflow
- Update brief as you go
docs/
├── workflow/ # Process docs (AI reads these)
├── briefs/ # Work packages (active/completed)
├── context/ # Mission, architectural context
├── standards/ # Code/process standards
└── TAG_INDEX.json # Doc navigation
Mode discipline prevents context collapse. Don't code during exploration. Don't debate architecture during implementation.
Adapt: Constraints, tags, project specifics Keep: Core mode structure, TDD workflow, phase boundaries
See change protocol in workflow docs before modifying process.