Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/blueprint-writing
How to write Blueprint-quality blueprints that AI agents can consume effectively. Covers implementation-agnostic blueprint design, testable acceptance criteria, hierarchical structure, cross-referencing, blueprint templates, greenfield and rewrite patterns, blueprint compaction, and gap analysis. Trigger phrases: "write blueprints", "create blueprints", "blueprint this out", "define requirements for agents", "how to write blueprints for AI"
Passed 18 of 22 test cases with the skill, and 11 of 22 without it.
and 9 more in the full report
9 fixed10 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our gap analysis report, we categorized a partially working payment feature as 'In Progress' and an unused helper library as 'Redundant'. Do these match the required gap analysis completion states?
| Checked | Without skill | With skill |
|---|---|---|
| The response corrects the states to use the standard taxonomy: Complete, Partial, Missing, and Over-built. | Missed | Passed |
The instructions your model reads when the skill loads.
Blueprints are implementation-agnostic. They define what the system must do and how to verify it, but never prescribe a specific framework, language, or architecture.
This is the fundamental distinction in Blueprint:
When blueprints avoid prescribing HOW, they become:
Bad blueprint requirement: "Use React useState hook to manage form state" Good blueprint requirement: "Form state persists across user interactions within a session. Acceptance: entering values, navigating away, and returning preserves all entered values."
This is the single most important rule in Blueprint writing. If an agent cannot automatically validate a requirement, that requirement will not be met.
Every requirement must answer: "How would an automated test verify this?"
| Weak Criterion | Strong Criterion |
|---|---|
| "UI should look good" | "All interactive elements have minimum 44x44px touch targets" |
| "System should be fast" | "API responses return within 200ms at p95 under 100 concurrent users" |
| "Handle errors gracefully" | "Network failures display a retry prompt with exponential backoff (1s, 2s, 4s)" |
| "Support authentication" | "Valid credentials return a session token; invalid credentials return 401 with error message" |
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.