Concepts
Lanes and methods
Every request goes through one of three lanes; the method decides how much proof a change needs.
The agent names the lane before it starts, so you can redirect early.
| Lane | When | What happens |
|---|---|---|
| Answer | Questions, exploration | Read-only. |
Fast-track (feature skill) | ≤ 3 files and no schema, permission or money change | A feature file in work/features/ with tasks and evidence; a behaviour change also edits its living spec. |
Spec (spec skill) | Everything bigger or riskier | A change: proposal + delta specs → your approval → plan → tasks → implement → verify every scenario → merge into the living specs. |
Fast-track work that grows past the threshold moves to the spec lane. Ticking a task always needs evidence: the command run and its result.
Methods
Chosen at setup (methodology in agent-kit.json):
| Method | What it requires |
|---|---|
| SDD | Every scenario is proven by a test or a reproducible check; tests are written where logic warrants them. |
| SDD + TDD | A failing test before every behaviour change (tdd skill: red → green → refactor, cases chosen with ZOMBIES). agent-kit tdd status lists changed logic without tests and preflight blocks it. |
Paths in testIgnore (thin route handlers, for example) are exempt from the TDD check.