agent-kit
Guides

A fast-track change

Small changes with a feature file, evidence, and the living spec kept true.

Example: "Rename the Sign out button on the home page to Log out."

  1. Lane check — ≤ 3 files, no schema, permission or money change. Otherwise the agent says so and uses the spec lane.
  2. Feature file — agent-kit work new feature rename-logout creates work/features/NNN-rename-logout.md with the goal and tasks (skipped for a one-line edit).
  3. Do the work — logic changes go test-first in SDD + TDD.
  4. Keep the living spec true — if a living spec describes this behaviour (home.R1 — Sign out), the agent edits the requirement or scenario in place, runs agent-kit specs lint home and agent-kit qa sync. A new requirement or capability isn't fast-track.
  5. Evidence and finish — each task ticked with the check run; project checks; status: done.

A change, end to end

The spec lane step by step — proposal, delta specs, approval, test-first tasks, verification, merge.

The TDD loop

Red, green, refactor — one behaviour at a time, cases from the scenarios and ZOMBIES.