skills.rest
iurykrieger
iurykriegerCOMMUNITY
Explore all skills by this author →
GitHub

acceptance-contract

Generate an Acceptance Contract from approved PRD and Tech Spec with BDD scenarios.

2|Updated Apr 25, 2026
Search Tags:#automation#qa#bdd#sprint#binding#acceptance-contract
One-click install
npx skills add https://github.com/iurykrieger/claude-yoke --skill acceptance-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acceptance-contract
Source: https://github.com/iurykrieger/claude-yoke/tree/main/skills/acceptance-contract
Command: npx skills add https://github.com/iurykrieger/claude-yoke --skill acceptance-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 3 — Acceptance Contract automatically converts approved PRD and Tech Spec into a binding document that codifies verification criteria and the ratification workflow.

Core Features & Use Cases

  • Generates a formal Acceptance Contract at .yoke/acceptance-contracts/<slug>.md for every sprint, with a 1:1 mapping from Task anchors to BDD scenarios.
  • Reads approved PRD and Tech Spec to derive scope, dependencies, and regulatory considerations; integrates sensor discovery outputs to populate verification steps.
  • Enables Trigger-3 ratification flow with a verifiable binding statement and a shared approval menu to decide whether to proceed to Phase 4.

Quick Start

Run the /yoke:acceptance-contract command after you have approved the PRD and Tech Spec to draft the Acceptance Contract and present the binding statement for ratification.

Frequently Asked Questions about acceptance-contract

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

FAQPage Schema
How do I generate BDD scenarios from a PRD and Tech Spec?▼

To generate BDD scenarios from a PRD and Tech Spec, this Skill produces a binding Acceptance Contract that maps each sprint task anchor to a separate BDD scenario with measurable validation criteria.

What is an acceptance contract in sprint automation?▼

An acceptance contract in sprint automation is a formal document that codifies verification criteria and ratification workflows, derived directly from approved upstream artifacts to ensure regulatory compliance.

How do I turn task anchors into BDD scenarios for verification?▼

You can turn task anchors into BDD scenarios by running the acceptance contract command, which automatically maps each ### Task <ID> anchor from your spec to an individual BDD scenario for measurable validation.

Do I need a configured .yoke directory to create acceptance contracts?▼

Yes, you need a configured host with .yoke/config.yaml, approved upstream artifacts in .yoke/prds and .yoke/specs, and sensor discovery data from CLAUDE.md to create acceptance contracts.

How does the ratification workflow function after drafting an acceptance contract?▼

The ratification workflow functions by presenting a verifiable binding statement and a shared approval menu, enabling a Trigger-3 flow to decide whether to proceed to Phase 4.

What are the limitations of automating acceptance contracts with BDD?▼

A limitation is that automating acceptance contracts requires strictly approved upstream PRD and Tech Spec artifacts, along with configured sensor discovery data, meaning unstructured or unapproved documents cannot be processed.

Related Skills

Explore More Software Engineering Skills→
iurykriegeriurykrieger
2

consolidate-sensors

Distill runtime verdicts and progress into per-sensor append-only bullets with citations.

Community
Advanced
withAIcolleaguewithAIcolleague

feature-planner

Convert vague feature ideas into phase-based roadmaps with approval gates.

Community
Advanced
0xHoneyJar0xHoneyJar
2

validating

Validate UI sprint components' physics and rigor compliance via Markdown reports.

Official
Intermediate
ilandahanilandahan
9

role-tech-lead

Guide Tech Lead teams through architecture decisions and code review criteria.

Community
Advanced