Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →odradekai/blueprinting
Use when planning new bundle-plugins, splitting complex skills, combining skills into bundles, or exploring a vague idea about packaging skills
Passed 17 of 22 test cases with the skill, and 3 of 22 without it.
and 15 more in the full report
14 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just invoked `bundles-forge:scaffolding` for our new project design. What condition must be met before we can proceed to the content authoring step?
| Checked | Without skill | With skill |
|---|---|---|
| The response requires the scaffolding inspector self-check to pass with 0 critical findings before moving to authoring. | Missed | Passed |
The instructions your model reads when the skill loads.
Turn a vague idea ("I want to package my skills") into a concrete project blueprint through needs exploration, architecture design, and structured review — then orchestrate the full creation pipeline: scaffolding, content authoring, workflow wiring, and initial quality check.
Core principle: Understand what you're building — and why — before generating anything. Five minutes of needs exploration saves hours of rework.
Skill type: Hybrid pattern — follow the three-phase process rigidly, but question selection, depth, and approach recommendations adapt to user context.
Announce at start: "I'm using the blueprinting skill to plan your bundle-plugin."
| Agent Reasoning | Reality |
|---|---|
| "The user's requirements are already clear" | Seemingly clear requirements often miss platform, workflow, and visibility architecture decisions |
| "This is just packaging a few existing skills" | Even simple packaging requires compatibility verification, cross-reference validation, and workflow chain mapping |
| "Moving fast through the process is more efficient" | Five minutes of exploration saves hours of rework from missing architecture decisions |
This skill handles three scenarios. All three feed into the same three-phase interview — only the initial context differs.
references/decomposition-analysis.md, then enters the interview with richer context. Splitting produces a new project. To refactor skills within an existing project, use bundles-forge:optimizing (Skill & Workflow Restructuring target).references/composition-analysis.md, then enters the interview with richer contextIf the user has an existing skill they want to break apart, start with Scenario B. If the user has multiple existing skills they want to combine into a new unified project, start with Scenario C. Otherwise, start with Scenario A.
Adding skills to an existing project? That's optimization, not blueprinting. Use
bundles-forge:optimizing(Skill & Workflow Restructuring target).
Read references/dialogue-strategies.md for the full interview protocol. Core principles: ask 1-2 questions at a time, reject vague answers, propose approaches with trade-offs, challenge over-scoping, surface contradictions immediately, and confirm understanding after each phase.
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.