Adwave
Adwave logo

Ship a feature

End-to-end recipe for landing a non-trivial but well-understood change. For high-stakes, unfamiliar, or decision-heavy work, use plan-then-build instead (/plan → /review-plan → implement → /review-build).

  1. Plan — planning-a-change: explore the code, write and stress-test a short plan.
  2. Implement — smallest safe change first, following existing patterns.
  3. Test — writing-tests: cover the new behavior, edge cases, and error paths (not just lines — test-coverage); bug fixes get a failing-then-passing test (regression-test).
  4. Verify — run the gate command; show the evidence. 4b. Session surfaces — when the change added or updated a user-visible surface (UI/API/CLI/MCP/job/flag), run verifying-session-surfaces (/verify-surfaces) before claiming the feature works. Live evidence, then root-cause-fix any BROKEN. Skip only for library-only diffs with no reachable consumer, and say so.
  5. Update docs in the same change — updating-docs: README/API/docstrings/config/changelog for anything the change altered (documentation-updates). 5b. In-flight check — after substantial edits, before claiming done, run deep-flight (/deep-flight): chosen layer still holds, shortcut RECEIPT, quoted gates, readonly flight-checker. Not deep-dive.
  6. Review the build — review-build (/review-build): ground-truth diff, plan/request trace, shortcut sweep, gate with pasted output. Prefer a fresh chat when stakes are above a one-file tweak. Skip only for truly trivial diffs, and say so.
  7. Review (maker ≠ checker) — dispatch the reviewer agent on the diff vs the plan. Fix correctness/intent gaps; ignore over-engineering suggestions. 7b. Post-flight (optional, same session) — when the user asks for a final pass, or the session accumulated deferred work / multi-surface fixes, run post-flight (/post-flight) before wrapping up.
  8. Commit & PR — writing-commit-messages, then opening-a-pr with a validation-first description. For a noisy or large diff, making-a-pr-reviewable first (tidy history, reviewer guidance).

Run each step as a verified loop (agentic-loop): write the stop contract, verify against ground truth, keep edits unstaged. Hand-off: planning-a-change produces the plan the reviewer checks against. The state file records what’s done so a resumed run continues cleanly.