Menu
Use when creating a new blueprint — generates the full directory structure with placeholder files and inline hints for each section.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
A living product specification skill. Use when you want to document how a system works, capture user stories and flows, build shared vocabulary, discuss existing functionality, or create a single source of truth for a feature or product area.
Use when reviewing an existing blueprint for gaps, missing flows, terminology conflicts, coverage of error cases, or untestable requirements.
Use when a system already exists but is not documented — to capture how it actually works, build shared vocabulary around it, and produce a living spec that the team can reason about and discuss.
Use when building a blueprint from scratch through conversation — specifying a new feature, capturing a planned system, or turning stakeholder descriptions into a structured living spec.
Use when evaluating a proposed change to a system described in a blueprint — a new feature, behaviour change, rule modification, or scope expansion. Convenes the review panel.
Use when reviewing a draft or existing blueprint for quality — missing scenarios, terminology gaps, unclear requirements. Convenes the review panel for a structured debate.
| name | scaffold |
| description | Use when creating a new blueprint — generates the full directory structure with placeholder files and inline hints for each section. |
Generate the directory structure for a new blueprint with placeholder files and comment hints for each section.
Blueprint name — what is this blueprint about? (used for directory name and title)
Scope — one sentence describing what this blueprint covers
Spec owner — who is accountable for accuracy?
Related blueprints — are there adjacent blueprints this one touches?
