Blueprinting (Bundle-Plugin Design)
Turns a vague "I want to package my skills" idea into an approved design document through a three-phase interview, then orchestrates scaffolding, authoring, wiring, and auditing.
What it does
blueprinting forces a planning stage before any files are generated for a Claude Code skill bundle-plugin.
- Phase 1 — Needs exploration: asks 1–2 questions at a time about the problem, target users, core capabilities, usage flow, and existing alternatives; rejects vague answers and restates understanding at a checkpoint.
- Phase 2 — Architecture design: recommends quick vs adaptive mode, validates a kebab-case project name, picks target platforms, proposes 2–3 skill decomposition options with trade-offs, maps the workflow chain, and decides bootstrap strategy.
- Phase 3 — Design doc & review: compiles a document from a template, self-reviews for TBDs, internal consistency, scope, and ambiguity, then waits for explicit user approval (hard gate).
- Orchestration pipeline: after approval it invokes scaffolding → authoring → workflow wiring → auditing, each with verify conditions and on-fail handling.
Three entry scenarios are supported: new project, decomposing an over-large skill, or composing several existing skills.
Who it's for
- Developers packaging multiple Claude Code skills into a distributable plugin/bundle.
- Anyone whose single SKILL.md has grown too large and needs splitting.
- Teams standardizing internal skill assets.
- Not relevant if you only consume skills rather than build them.
Examples
- Plan a new bundle: say "I want a frontend code-review skill set" and it interviews you, proposes a 3–4 skill decomposition, and produces a design doc before scaffolding.
- Split a monolith: point it at a 1,000-line
my-devops/SKILL.mdand it maps responsibilities and proposes deploy / monitor / rollback skills. - Compose scattered skills: with six loose skills, it checks naming conflicts and overlapping responsibilities, then plans one bundle with a bootstrap routing table.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/OdradekAI/bundles-forge/HEAD/skills/blueprinting/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the skills/blueprinting folder from the GitHub repo OdradekAI/bundles-forge into my ~/.claude/skills/blueprinting/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/OdradekAI/bundles-forge.git && mkdir -p ~/.claude/skills && cp -r bundles-forge/skills/* ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal and go to a temp folder, e.g.
cd ~/Downloads - Clone the repo:
git clone https://github.com/OdradekAI/bundles-forge.git - Create the skills folder if needed:
mkdir -p ~/.claude/skills - This skill depends on sibling skills (scaffolding, authoring, auditing, optimizing) and its
references/files, so copy the whole set:cp -r bundles-forge/skills/* ~/.claude/skills/ - Verify with
ls ~/.claude/skills/blueprinting— you should see SKILL.md and a references folder. - Restart Claude Code and say something like "help me plan a new skill bundle".
- Note: nothing is generated until you approve the design document, so review it carefully before saying yes.