blueprinting

Name: blueprinting
Author: OdradekAI

290stars23forks

How to install blueprinting?

odradekai/bundles-forge/blueprinting

$npx -y skills add OdradekAI/bundles-forge --skill blueprinting

Installs into the current project.

Summary

Use when planning new bundle-plugins, splitting complex skills, combining skills into bundles, or exploring a vague idea about packaging skills

Files · 1

View on GitHub

SKILL.md

1	# Blueprinting Bundle-Plugins
2
3	## Overview
4
5	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.
6
7	Core principle: Understand what you're building — and why — before generating anything. Five minutes of needs exploration saves hours of rework.
8
9	Skill type: Hybrid pattern — follow the three-phase process rigidly, but question selection, depth, and approach recommendations adapt to user context.
10
11	Announce at start: "I'm using the blueprinting skill to plan your bundle-plugin."
12
13	<HARD-GATE>
14	Do NOT invoke bundles-forge:scaffolding or any subsequent orchestration phase until the user has approved the design document. Every project — regardless of perceived simplicity — must pass through needs exploration → architecture design → design document review. Quick mode may shorten the process (needs exploration asks only 2 core questions), but it cannot skip it.
15	</HARD-GATE>
16
17	\| Agent Reasoning \| Reality \|
18	\|-----------------\|---------\|
19	\| "The user's requirements are already clear" \| Seemingly clear requirements often miss platform, workflow, and visibility architecture decisions \|
20	\| "This is just packaging a few existing skills" \| Even simple packaging requires compatibility verification, cross-reference validation, and workflow chain mapping \|
21	\| "Moving fast through the process is more efficient" \| Five minutes of exploration saves hours of rework from missing architecture decisions \|
22
23	## Three Entry Points
24
25	This skill handles three scenarios. All three feed into the same three-phase interview — only the initial context differs.
26
27	- Scenario A: New project from scratch — Begin with Context Exploration, then the full interview
28	- Scenario B: Splitting an existing complex skill — Context Exploration reads the existing skill via `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).
29	- Scenario C: Composing multiple existing skills — Context Exploration inventories candidates via `references/composition-analysis.md`, then enters the interview with richer context
30
31	If 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.
32
33	> Adding skills to an existing project? That's optimization, not blueprinting. Use `bundles-forge:optimizing` (Skill & Workflow Restructuring target).
34
35	## Dialogue Strategy
36
37	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.
38
39	## Context Exploration
40
41	Before asking any questions, gather available context:
42
43	### Scenario A (New Project)
44	1. Scan the workspace — look for scattered skill files, existing SKILL.md drafts, or relevant project files that hint at what the user is building
45	2. If user context is already rich from their initial message, proceed directly to Phase 1
46
47	### Scenario B (Decomposition)
48	1. Read the existing skill — follow `references/decomposition-analysis.md` to map responsibilities, identify split points, and propose a decomposition
49	2. Present the decomposition proposal to the user for approval
50	3. Proceed to Phase 1 with the decomposition as input context. In Phase 1, skip questions already answered by the decomposition analysis. Confirm those answers with the user rather than re-asking.
51
52	### Scenario C (Composition)
53	1. Inventory candidate skills — follow `references/composition-analysis.md` to check compatibility, detect conflicts, and design orchestration
54	2. Present the composition plan to the user for approval
55	3. Proceed to Phase 1 with the composition analysis as input context. In Phase 1, skip questions already answered by the composition analysis. Confirm those answers with the user rather than re-asking.
56
57	## Phase 1: Needs Exploration
58
59	Understand what the user wants to build and why, before making any architecture decisions. Ask these one at a time, adapting based on answers.
60
61	### 1. Problem Scenario
62
63	Ask: "What problem does this skill bundle solve? How are people solving it today?"
64
65	Understand the gap between the current state and what the user envisions. This is the foundation for all subsequent decisions.
66
67	### 2. Target Users
68
69	Ask: "Who will use this skill bundle?

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

blueprinting

290stars23forks

View on GitHub

How to install blueprinting?

odradekai/bundles-forge/blueprinting

$npx -y skills add OdradekAI/bundles-forge --skill blueprinting

Installs into the current project.

Summary

Use when planning new bundle-plugins, splitting complex skills, combining skills into bundles, or exploring a vague idea about packaging skills

Files · 1

View on GitHub

SKILL.md

1	# Blueprinting Bundle-Plugins
2
3	## Overview
4
5	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.
6
7	Core principle: Understand what you're building — and why — before generating anything. Five minutes of needs exploration saves hours of rework.
8
9	Skill type: Hybrid pattern — follow the three-phase process rigidly, but question selection, depth, and approach recommendations adapt to user context.
10
11	Announce at start: "I'm using the blueprinting skill to plan your bundle-plugin."
12
13	<HARD-GATE>
14	Do NOT invoke bundles-forge:scaffolding or any subsequent orchestration phase until the user has approved the design document. Every project — regardless of perceived simplicity — must pass through needs exploration → architecture design → design document review. Quick mode may shorten the process (needs exploration asks only 2 core questions), but it cannot skip it.
15	</HARD-GATE>
16
17	\| Agent Reasoning \| Reality \|
18	\|-----------------\|---------\|
19	\| "The user's requirements are already clear" \| Seemingly clear requirements often miss platform, workflow, and visibility architecture decisions \|
20	\| "This is just packaging a few existing skills" \| Even simple packaging requires compatibility verification, cross-reference validation, and workflow chain mapping \|
21	\| "Moving fast through the process is more efficient" \| Five minutes of exploration saves hours of rework from missing architecture decisions \|
22
23	## Three Entry Points
24
25	This skill handles three scenarios. All three feed into the same three-phase interview — only the initial context differs.
26
27	- Scenario A: New project from scratch — Begin with Context Exploration, then the full interview
28	- Scenario B: Splitting an existing complex skill — Context Exploration reads the existing skill via `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).
29	- Scenario C: Composing multiple existing skills — Context Exploration inventories candidates via `references/composition-analysis.md`, then enters the interview with richer context
30
31	If 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.
32
33	> Adding skills to an existing project? That's optimization, not blueprinting. Use `bundles-forge:optimizing` (Skill & Workflow Restructuring target).
34
35	## Dialogue Strategy
36
37	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.
38
39	## Context Exploration
40
41	Before asking any questions, gather available context:
42
43	### Scenario A (New Project)
44	1. Scan the workspace — look for scattered skill files, existing SKILL.md drafts, or relevant project files that hint at what the user is building
45	2. If user context is already rich from their initial message, proceed directly to Phase 1
46
47	### Scenario B (Decomposition)
48	1. Read the existing skill — follow `references/decomposition-analysis.md` to map responsibilities, identify split points, and propose a decomposition
49	2. Present the decomposition proposal to the user for approval
50	3. Proceed to Phase 1 with the decomposition as input context. In Phase 1, skip questions already answered by the decomposition analysis. Confirm those answers with the user rather than re-asking.
51
52	### Scenario C (Composition)
53	1. Inventory candidate skills — follow `references/composition-analysis.md` to check compatibility, detect conflicts, and design orchestration
54	2. Present the composition plan to the user for approval
55	3. Proceed to Phase 1 with the composition analysis as input context. In Phase 1, skip questions already answered by the composition analysis. Confirm those answers with the user rather than re-asking.
56
57	## Phase 1: Needs Exploration
58
59	Understand what the user wants to build and why, before making any architecture decisions. Ask these one at a time, adapting based on answers.
60
61	### 1. Problem Scenario
62
63	Ask: "What problem does this skill bundle solve? How are people solving it today?"
64
65	Understand the gap between the current state and what the user envisions. This is the foundation for all subsequent decisions.
66
67	### 2. Target Users
68
69	Ask: "Who will use this skill bundle?

People who liked this also viewed

6 picks

Type