What problem does it solve? Teams often start implementation without a shared, testable definition of done, leading to scope creep, vague acceptance criteria, and disputes during review. This Skill defines Sprint Contracts before any file is edited, so implementers and evaluators agree on measurable outcomes upfront. ## Core Features & Use Cases - Contract Authoring: Produces a hybrid JSON frontmatter plus Markdown contract with testable acceptance criteria, Harness pillar criteria (reliability, scalability, security, observability, maintainability), and explicit out-of-scope sections. - Negotiation Protocol: Manages a structured implementer-verifier review loop with a negotiation log, a maximum of two amendment cycles, and supervisor escalation on deadlock. - Evaluation Protocol: Grades each criterion as PASS, PARTIAL, or FAIL against hard thresholds, writing feedback and verdict JSON files for re-evaluation of only failed criteria. - Use Case: A backend engineer is assigned a Tier 2 task to add a refund endpoint. Before coding, they draft a contract with criteria like "idempotency key prevents duplicate refunds, verified by npm run test", negotiate it with the Verifier, and later the QA Agent evaluates the implementation against those exact thresholds. ## Quick Start Ask the agent to write a sprint contract for your Tier 2 task, including the goal, testable acceptance criteria, and relevant Harness pillar criteria.
