contract

Name: contract
Availability: InStock
Author: tesserine

Define verifiable Given/When/Then contracts across behavior, documentation, and code quality.

Updated Mar 3, 2026

Search Tags:#documentation #verification #evidence #code-quality #bdd #contract #acceptance-criteria

Ready to run

npx skills add https://github.com/tesserine/groundwork --skill contract-tesserine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contract
Source: https://github.com/tesserine/groundwork/tree/main/skills/contract
Command: npx skills add https://github.com/tesserine/groundwork --skill contract-tesserine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The contract discipline provides a single, authoritative home for defining what done means across behavior, documentation, and code quality, ensuring every change carries an observable, evidence-backed contract rather than drifting.

Core Features & Use Cases

Contract-first authoring: refine acceptance criteria into Given/When/Then scenarios and declare documentation or code-quality obligations.
Evidence-driven lifecycle: connect work-unit inputs to validation, implementation, verification, and landing with a single source of truth.
Teeth-based completeness: require hollow or stub deliveries to fail against each criterion, preventing silent success.

Quick Start

Draft a contract blueprint at the start of a work-unit and map each acceptance criterion to a Given/When/Then scenario

Frequently Asked Questions about contract

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

FAQPage Schema

How do I enforce verifiable acceptance criteria across code changes?▼

To enforce verifiable acceptance criteria, draft a contract blueprint mapping each criterion to Given/When/Then scenarios, then validate implementation against this evidence trail during verification and landing phases.

What is contract-driven development and how does it prevent hollow deliveries?▼

Contract-driven development defines explicit Given/When/Then scenarios and uses teeth-based completeness checks to ensure stub deliveries fail against each criterion, preventing silent success and drift.

How do I ensure documentation and code quality obligations are traceable to evidence?▼

Ensure traceability by using a contract blueprint as a single source of truth, declaring documentation and code-quality obligations alongside behavioral scenarios to guide every phase from planning to landing.

Can I apply BDD contracts to the verification and landing phases?▼

Yes, BDD contracts apply to verification and landing phases by requiring explicit Given/When/Then scenarios and an evidence trail that validates work claims are traceable before completing a change.

What is the best way to prevent silent success when delivering code stubs?▼

The best way to prevent silent success is implementing teeth-based completeness checks that require hollow or stub deliveries to fail against each declared Given/When/Then contract criterion.

When do I need to define a contract blueprint for a work unit?▼

Define a contract blueprint at the start of a work unit to map each acceptance criterion to a Given/When/Then scenario, ensuring behavior, documentation, and code quality are guided by a concrete contract.