sprint-contracts

Coordinate machine-verified sprint contracts between generator and evaluator agents.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill sprint-contracts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-contracts
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/sprint-contracts
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill sprint-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes structured, machine-verifiable sprint contracts between generator and evaluator agents to define acceptance criteria before implementation.

Core Features & Use Cases

  • Drafts contract criteria with inputs, outputs, and invariants per criterion.
  • Supports negotiation loops with iterative refinement until agreement.
  • Stores contract history and iteration data for audit and reproducibility.

Quick Start

Draft and negotiate a machine-verifiable sprint contract between generator and evaluator teams before implementing a feature.

Frequently Asked Questions about sprint-contracts

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

FAQPage Schema
How do I define machine-verifiable sprint contracts for autonomous agents?

Sprint contracts define feature acceptance criteria by specifying inputs, outputs, and invariants. This formalizes agreements between generator and evaluator agents before implementation begins in autonomous development workflows.

What is a sprint contract negotiation loop in agent-driven development?

A sprint contract negotiation loop is an iterative refinement process between generator and evaluator agents. They cycle through contract criteria until both reach a mutual agreement on the formalized feature acceptance standards.

How do I generate test stubs from sprint acceptance criteria?

You can auto-generate test stubs directly from specified contract criteria. The system uses the defined inputs, outputs, and invariants to create the baseline tests required for machine verification during the sprint.

Can I persist and version sprint contract history for audit reproducibility?

Yes, the system persists iteration data and contract history in the .harness/contracts directory. This provides full versioning support to ensure auditability and reproducibility across feature sprints.

Do I need a dedicated environment to track sprint contracts across iterations?

You need an autonomous agent-driven development workflow with generator and evaluator agents. The system handles the contract tracking internally, storing iteration history directly within the .harness/contracts directory structure.