brainstorming-extension

Name: brainstorming-extension
Author: dsifry

361stars51forks

How to install brainstorming-extension?

dsifry/metaswarm/brainstorming-extension

$npx -y skills add dsifry/metaswarm --skill brainstorming-extension

Installs into the current project.

Summary

Enforces design review gate after brainstorming — bridges superpowers:brainstorming into the metaswarm quality pipeline

Files · 1

View on GitHub

SKILL.md

1	# Brainstorming Extension - Mandatory Review Gate Bridge
2
3	## Purpose
4
5	This skill bridges `superpowers:brainstorming` into the metaswarm quality pipeline by enforcing the Design Review Gate after any design document is created. Without this bridge, brainstorming flows directly into `writing-plans`, bypassing the 5-agent design review that catches architectural, security, and requirements issues before expensive implementation begins.
6
7	This is a critical workflow enforcement point, not a passive extension.
8
9	---
10
11	## The Problem This Solves
12
13	`superpowers:brainstorming` has a built-in terminal state: "The ONLY skill you invoke after brainstorming is writing-plans." This creates a pipeline bypass:
14
15	```text
16	WITHOUT this extension (broken flow):
17
18	superpowers:brainstorming
19	└── Commits design doc
20	└── writing-plans (DIRECTLY — no review!)
21	└── executing-plans
22	└── Implementation begins on UNREVIEWED design
23	```
24
25	```text
26	WITH this extension (correct flow):
27
28	superpowers:brainstorming
29	└── Commits design doc
30	│
31	▼
32	┌─────────────────────────────────────────┐
33	│ MANDATORY DESIGN REVIEW GATE │
34	│ (Enforced by CLAUDE.md + start-task) │
35	│ │
36	│ 5 parallel review agents: │
37	│ • Product Manager (use cases) │
38	│ • Architect (architecture) │
39	│ • Designer (UX/API) │
40	│ • Security Design (threats) │
41	│ • CTO (TDD readiness) │
42	│ │
43	│ ALL FIVE must APPROVE │
44	└─────────────────────────────────────────┘
45	│
46	▼
47	ALL APPROVED? ────No────► Iterate on design (max 3)
48	│
49	Yes
50	│
51	▼
52	writing-plans → plan-review-gate → orchestrated-execution
53	```
54
55	---
56
57	## How Enforcement Works
58
59	YAML frontmatter triggers (`auto_activate`, `triggers`) are metadata hints — Claude Code does not enforce them automatically. Instead, this enforcement works through three redundant mechanisms:
60
61	### 1. CLAUDE.md Template (Primary)
62
63	The CLAUDE.md template contains a "Workflow Enforcement (MANDATORY)" section that explicitly states:
64
65	> After brainstorming: STOP → Run Design Review Gate → Wait for all 5 agents to APPROVE → Only then proceed
66
67	This instruction is loaded into every conversation and overrides conflicting skill instructions.
68
69	### 2. start-task Command (Secondary)
70
71	The `/start-task` command's Problem Definition Phase includes an explicit "MANDATORY HANDOFF" block that requires the design review gate after brainstorming.
72
73	### 3. This Skill Document (Reference)
74
75	When this skill is loaded (either by name or auto-activation), it provides the detailed procedure below.
76
77	---
78
79	## Procedure: After Brainstorming Completes
80
81	When `superpowers:brainstorming` commits a design document:
82
83	### Step 1: Announce the Gate
84
85	```markdown
86	## Design Review Gate Activated
87
88	Your design document has been committed. Before proceeding to implementation,
89	I'll run it through our 5-agent review panel.
90
91	Spawning reviews:
92	- Product Manager Agent (use case/requirements validation)
93	- Architect Agent (technical architecture)
94	- Designer Agent (UX/API design)
95	- Security Design Agent (threat modeling/security review)
96	- CTO Agent (TDD readiness)
97
98	This typically takes 2-3 minutes...
99	```
100
101	### Step 2: Invoke the Design Review Gate
102
103	Invoke the `design-review-gate` skill with the path to the design document. This spawns all 5 review agents in parallel.
104
105	### Step 3: Report Results
106
107	If ALL APPROVED:
108
109	```markdown
110	## Design Review Gate: PASSED
111
112	All five reviewers have approved your design!
113
114	\| Agent \| Verdict \| Notes \|
115	\| --------------- \| -------- \| ------------------------------------- \|
116	\| Product Manager \| APPROVED \| Clear use cases, measurable benefits \|
117	\| Architect \| APPROVED \| Clean architecture, follows patterns \|
118	\| Designer \| APPROVED \| Good API design, clear error states \|
119	\| Security Design \| APPROVED \| No high-risk threats, mitigations OK \|
120	\| CTO \| APPROVED \| TDD specs present, ready to implement \|
121
122	### Next Steps
123	1. Create epic for this feature
124	2. Create implementation plan (writing-plans)
125	3. Run plan through Plan Review Gate (3 adversarial reviewers)
126	4. Set up worktree for isolated development
127	5. Begin orchestrated execution
128
129	Ready to proceed? [Yes / No]
130	```
131
132	If ANY NEEDS_REVISION:
133
134	```markdown
135	## Design Review Gate: NEEDS REVISION
136
137	Some reviewers found issues that need to be addressed.
138
139	### Blocking Issues
140	[Agent-specific issues listed here]
141
142	### Questions Requiring Answers
143	[Questions listed

People who liked this also viewed

6 picks

Type

paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026157k5
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026154k259k
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026143k259k
browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 202685k4.6k
wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 202675k182k
wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 202666k137

brainstorming-extension

361stars51forks

View on GitHub

How to install brainstorming-extension?

dsifry/metaswarm/brainstorming-extension

$npx -y skills add dsifry/metaswarm --skill brainstorming-extension

Installs into the current project.

Summary

Enforces design review gate after brainstorming — bridges superpowers:brainstorming into the metaswarm quality pipeline

Files · 1

View on GitHub

SKILL.md

1	# Brainstorming Extension - Mandatory Review Gate Bridge
2
3	## Purpose
4
5	This skill bridges `superpowers:brainstorming` into the metaswarm quality pipeline by enforcing the Design Review Gate after any design document is created. Without this bridge, brainstorming flows directly into `writing-plans`, bypassing the 5-agent design review that catches architectural, security, and requirements issues before expensive implementation begins.
6
7	This is a critical workflow enforcement point, not a passive extension.
8
9	---
10
11	## The Problem This Solves
12
13	`superpowers:brainstorming` has a built-in terminal state: "The ONLY skill you invoke after brainstorming is writing-plans." This creates a pipeline bypass:
14
15	```text
16	WITHOUT this extension (broken flow):
17
18	superpowers:brainstorming
19	└── Commits design doc
20	└── writing-plans (DIRECTLY — no review!)
21	└── executing-plans
22	└── Implementation begins on UNREVIEWED design
23	```
24
25	```text
26	WITH this extension (correct flow):
27
28	superpowers:brainstorming
29	└── Commits design doc
30	│
31	▼
32	┌─────────────────────────────────────────┐
33	│ MANDATORY DESIGN REVIEW GATE │
34	│ (Enforced by CLAUDE.md + start-task) │
35	│ │
36	│ 5 parallel review agents: │
37	│ • Product Manager (use cases) │
38	│ • Architect (architecture) │
39	│ • Designer (UX/API) │
40	│ • Security Design (threats) │
41	│ • CTO (TDD readiness) │
42	│ │
43	│ ALL FIVE must APPROVE │
44	└─────────────────────────────────────────┘
45	│
46	▼
47	ALL APPROVED? ────No────► Iterate on design (max 3)
48	│
49	Yes
50	│
51	▼
52	writing-plans → plan-review-gate → orchestrated-execution
53	```
54
55	---
56
57	## How Enforcement Works
58
59	YAML frontmatter triggers (`auto_activate`, `triggers`) are metadata hints — Claude Code does not enforce them automatically. Instead, this enforcement works through three redundant mechanisms:
60
61	### 1. CLAUDE.md Template (Primary)
62
63	The CLAUDE.md template contains a "Workflow Enforcement (MANDATORY)" section that explicitly states:
64
65	> After brainstorming: STOP → Run Design Review Gate → Wait for all 5 agents to APPROVE → Only then proceed
66
67	This instruction is loaded into every conversation and overrides conflicting skill instructions.
68
69	### 2. start-task Command (Secondary)
70
71	The `/start-task` command's Problem Definition Phase includes an explicit "MANDATORY HANDOFF" block that requires the design review gate after brainstorming.
72
73	### 3. This Skill Document (Reference)
74
75	When this skill is loaded (either by name or auto-activation), it provides the detailed procedure below.
76
77	---
78
79	## Procedure: After Brainstorming Completes
80
81	When `superpowers:brainstorming` commits a design document:
82
83	### Step 1: Announce the Gate
84
85	```markdown
86	## Design Review Gate Activated
87
88	Your design document has been committed. Before proceeding to implementation,
89	I'll run it through our 5-agent review panel.
90
91	Spawning reviews:
92	- Product Manager Agent (use case/requirements validation)
93	- Architect Agent (technical architecture)
94	- Designer Agent (UX/API design)
95	- Security Design Agent (threat modeling/security review)
96	- CTO Agent (TDD readiness)
97
98	This typically takes 2-3 minutes...
99	```
100
101	### Step 2: Invoke the Design Review Gate
102
103	Invoke the `design-review-gate` skill with the path to the design document. This spawns all 5 review agents in parallel.
104
105	### Step 3: Report Results
106
107	If ALL APPROVED:
108
109	```markdown
110	## Design Review Gate: PASSED
111
112	All five reviewers have approved your design!
113
114	\| Agent \| Verdict \| Notes \|
115	\| --------------- \| -------- \| ------------------------------------- \|
116	\| Product Manager \| APPROVED \| Clear use cases, measurable benefits \|
117	\| Architect \| APPROVED \| Clean architecture, follows patterns \|
118	\| Designer \| APPROVED \| Good API design, clear error states \|
119	\| Security Design \| APPROVED \| No high-risk threats, mitigations OK \|
120	\| CTO \| APPROVED \| TDD specs present, ready to implement \|
121
122	### Next Steps
123	1. Create epic for this feature
124	2. Create implementation plan (writing-plans)
125	3. Run plan through Plan Review Gate (3 adversarial reviewers)
126	4. Set up worktree for isolated development
127	5. Begin orchestrated execution
128
129	Ready to proceed? [Yes / No]
130	```
131
132	If ANY NEEDS_REVISION:
133
134	```markdown
135	## Design Review Gate: NEEDS REVISION
136
137	Some reviewers found issues that need to be addressed.
138
139	### Blocking Issues
140	[Agent-specific issues listed here]
141
142	### Questions Requiring Answers
143	[Questions listed

People who liked this also viewed

6 picks

Type