sprint-contract

Negotiate and formalize sprint success criteria using markdown templates and JSON files.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ats-kinoshita-iso/trine-eval --skill sprint-contract-ats-kinoshita-iso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-contract
Source: https://github.com/ats-kinoshita-iso/trine-eval/tree/main/skills/sprint-contract
Command: npx skills add https://github.com/ats-kinoshita-iso/trine-eval --skill sprint-contract-ats-kinoshita-iso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized protocol and template for negotiating, defining, and documenting success criteria for development sprints, ensuring clarity and testability.

Core Features & Use Cases

  • Contract Template: Offers a comprehensive markdown template for drafting sprint success and failure criteria with clear tagging and weights.
  • Negotiation Protocol: Defines a structured process for Generator and Evaluator to collaboratively refine sprint contracts, focusing on testability and completeness.
  • Use Case: Teams adopting Agile practices can formalize their sprint goals and acceptance criteria, facilitating automated validation and audit.

Quick Start

Refer to template.md to create a new sprint contract, then review and refine it following the negotiation protocol.

Frequently Asked Questions about sprint-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define and track sprint success criteria in Agile workflows?

Sprint success criteria are defined using a markdown template and structured JSON files, enabling clear negotiation, testability, and automated tracking throughout development projects. This ensures cross-team alignment on what constitutes sprint completion.

What is a sprint contract and when do I need one for development projects?

A sprint contract is a standardized protocol document formalizing success and failure criteria for development sprints. You need one when adopting Agile practices to enhance clarity, testability, and cross-team communication regarding sprint goals.

How do I negotiate sprint goals and acceptance criteria with my team?

You negotiate sprint goals using a structured protocol where a Generator and Evaluator collaboratively refine the sprint contract, focusing on testability and completeness to ensure all acceptance criteria are clearly defined and validated.

Can I automate sprint validation and audits using structured contract templates?

Yes, sprint validation and audits can be automated using structured JSON files generated from the markdown contract template, allowing teams to programmatically track and verify sprint success criteria against defined acceptance metrics.

Does sprint-contract require any specific dependencies or frameworks to use?

No dependencies are required to use the sprint contract template. It operates independently using markdown templates and structured JSON files, making it applicable in any Agile development environment without prerequisite frameworks.

What are the limitations of using markdown templates for sprint contracts?

Markdown templates for sprint contracts require manual adherence to the negotiation protocol and do not enforce compliance automatically. Teams must collaboratively maintain discipline in refining and tagging success criteria with appropriate weights.