Finish

Overview

Turn “it works on my machine” into “this is ready to ship” by running verification, checking boundary discipline, and reporting changes in a consistent format.

Workflow

1. Re-check intent artifacts:
   • if contracts/semantics changed: specs/contracts are updated (spec)
   • if shared primitives were added/changed: API surface + adoption notes are clear (platform)
   • for non-trivial work: objective function, decision table, measurement ladder, and kill criteria are documented
2. Run verification (prefer narrow → broad):
   • unit tests / focused tests
   • typecheck
   • lint/format (if configured)
   • build (if relevant)
3. Boundary discipline spot-check (only where the change touched boundaries):
   • timeouts/cancellation/retry safety (resilience)
   • authn/authz + input validation + safe logging (security)
   • logs/traces/metrics correlation + low-cardinality labels (observability)
4. Cleanup:
   • remove dead code, debug logs, commented-out blocks
   • ensure errors are actionable and don’t leak secrets/PII
   • update quickstarts or runbooks if needed
5. Translation check:
   • write an executive packet (decision bandwidth)
   • write an engineer packet (implementation bandwidth)

Guardrails

• Don’t claim verification you didn’t run; report “not run” and why.
• Prefer explicit commands and outputs over vague statements (“tests passed”).
• Don’t expand scope; if you find unrelated issues, list as follow-ups.

Output Template

Return:

• Executive packet (non-trivial changes):
  • goal and decision/bet
  • primary trade-off and risk
  • success/failure signals + review ritual owner/cadence
  • kill criteria / reversal trigger
  • immediate next step
• Engineer packet:
  • what changed (3–7 bullets; behavior + contract impact)
  • files touched (key paths only)
  • verification (commands run + results, or why not run)
  • risks/follow-ups (including rollout watchpoints)