definition-of-ready

Execute Definition of Ready checks and generate coding agent instructions.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill definition-of-ready
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: definition-of-ready
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/definition-of-ready
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill definition-of-ready

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final gate check before a story is handed to the coding agent. It runs hard blocks (H1–H9, H-E2E, H-NFR through H-NFR3) and warnings (W1-W5), determines oversight level, and produces a coding agent instructions block when all hard blocks pass. Blocks are unambiguous - all must pass, no exceptions. Warnings require explicit acknowledgement. Use when test plan and review are complete and someone says "is this story ready", "definition of ready", "ready to code", or moves past /test-plan.

Core Features & Use Cases

  • Enforces unconditional hard-block pass for story handoff to coding agent.
  • Generates a ready-for-work Contract Proposal and a Contract Review sequence.
  • Supports governance context and oversight mapping for gating decisions.

Quick Start

Tell the system: "Is this story ready?" and run the DoR workflow.

Frequently Asked Questions about definition-of-ready

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

FAQPage Schema
What is a definition of ready workflow for agile user stories?

A definition of ready workflow enforces hard-block checks on a user story before handing it to a coding agent. It verifies entry conditions, generates contract proposals, and produces a coding instruction block only when all mandatory blocks pass.

How do I check if my user story is ready for a coding agent?

Check story readiness by triggering the DoR workflow to execute hard-block checks and warnings. All hard blocks must pass unconditionally, and any warnings require explicit acknowledgement before the story is approved for the coding agent.

When should I run definition of ready checks in the agile process?

Run definition of ready checks after the test plan and review are complete, acting as the final gate before story handoff. Use it when someone asks if a story is ready to code or when moving past the test-plan phase.

What happens if a user story fails a hard block check?

If a user story fails a hard block check, coding agent handoff is blocked entirely. All hard blocks must pass with no exceptions, and the failure state is documented in the DoR artefact and pipeline state files to ensure traceability.

Does the definition of ready process support governance and oversight mapping?

Yes, the definition of ready process supports governance context and determines oversight levels for gating decisions. It maintains blocks, warnings, and standards checks in DoR artefact and pipeline state files to ensure traceability and compliance.