blueprint

Convert requirements.md into an executable blueprint with contracts and verification gates.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/sr-ai-dev/sr-harness --skill blueprint-sr-ai-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/sr-ai-dev/sr-harness/tree/main/skills/blueprint
Command: npx skills add https://github.com/sr-ai-dev/sr-harness --skill blueprint-sr-ai-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sr-harness-cli.

What problem does it solve?

This Skill converts a requirements document into an execution-ready blueprint so downstream execution can proceed without rework, while preserving cross-module correctness through explicit contracts and verification gates.

Core Features & Use Cases

  • Contract-first planning: synthesizes cross-module interfaces and invariants to lock in how components talk before tasks are implemented.
  • Layered task graph planning: generates a scoped, layered DAG of tasks that fulfills every sub-requirement.
  • Journey detection: groups related sub-requirements into end-to-end user flows that warrant additional E2E verification.
  • Verify-plan gate assignment: assigns verification gates (machine, semantic, E2E, or human) per sub-requirement and journey based on what must be observed or judged.

Quick Start

Run the blueprint skill on your spec directory that contains requirements.md to generate plan.json and contracts.md.

Frequently Asked Questions about blueprint

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

FAQPage Schema
How do I turn requirements.md into an executable task graph?

Turn requirements.md into an executable task graph by deriving contracts, layered task dependencies, journeys, and verification gates into a structured plan.json file.

What is contract-first planning for software requirements?

Contract-first planning synthesizes cross-module interfaces and invariants before implementation, ensuring components interact correctly and reducing downstream rework.

How do I generate end-to-end user journeys from sub-requirements?

Generate end-to-end journeys by grouping related sub-requirements into user flows that warrant additional verification, assigning E2E gates to validate them.

Does this blueprint generation approach work for refactoring and bugfix specs?

Blueprint generation applies to greenfield, feature, refactor, and bugfix specs by grounding planning in repository structure and enforcing sub-requirement coverage.

How do I assign machine, semantic, E2E, and human verification gates to a plan?

Assign verification gates by evaluating what must be observed or judged per sub-requirement and journey, establishing machine, semantic, E2E, or human checks for verify_plan completeness.

Do I need sr-harness-cli to generate plan.json and contracts.md?

Yes, sr-harness-cli is a required dependency to run the blueprint skill and generate plan.json and contracts.md outputs from your requirements document.