Commit planning
A2C formalizes how work is split into batches that map to reviewable Git commits.
Why commit plans exist
Without a plan, AI-assisted work drifts into big-bang generation. A commit plan:
- defines the next bounded batch
- connects batches to architecture and ADRs
- gives prompts a stop condition
- keeps ADR decisions isolated in dedicated commits
Commit plan structure
Use pathname:///a2c-assets/templates/commit-plan/commit-plan-template.md.
Each batch should specify:
| Field | Purpose |
|---|---|
| Batch id | Stable reference for prompts (batch-01, etc.) |
| Goal | One-sentence outcome |
| Scope | Files and directories in scope |
| Out of scope | Explicit exclusions |
| Prerequisites | ADRs, docs, or prior batches required |
| Suggested commit message | Conventional or adr(...) type |
| Stop condition | When the agent must halt |
Ordering preferences
- Docs before code
- Architecture before scaffolding
- Scaffolding before implementation
- ADR decisions in dedicated
adr(<category>): ...commits - One coherent concern per commit
ADR commit isolation
An ADR commit may include only:
- the ADR file
- updates to
docs/adr/INDEX.md - supersedes / superseded-by link maintenance
- minimal metadata required for that ADR
An ADR commit must not include implementation, unrelated docs, or multiple ADRs.
Prompt integration
Phase prompts reference the current batch from the commit plan. Example:
Execute batch
bootstrap-02fromplans/bootstrap-a2c-workflow.md. Stop when batch scope is complete.