القائمة
Warmstart extension to superpowers:brainstorming - auto-triggers design review gate after design completion
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | brainstorming-extension |
| description | Warmstart extension to superpowers:brainstorming - auto-triggers design review gate after design completion |
| auto_activate | true |
| triggers | ["after:superpowers:brainstorming","design document committed"] |
This skill extends superpowers:brainstorming to automatically trigger the design review gate after a design document is created. It ensures complex features go through Product Manager, Architect, Designer, Security Design, and CTO review before implementation begins.
This is a Warmstart-specific extension that hooks into the superpowers brainstorming skill.
The standard brainstorming flow:
superpowers:brainstorming
│
├── Collaborative Q&A
├── Design sections with validation
├── Write to docs/plans/YYYY-MM-DD-<topic>-design.md
└── Commit to git
│
▼
"Ready to set up for implementation?"
With this extension:
superpowers:brainstorming
│
├── Collaborative Q&A
├── Design sections with validation
├── Write to docs/plans/YYYY-MM-DD-<topic>-design.md
└── Commit to git
│
▼
┌─────────────────────────────────────────┐
│ AUTOMATIC DESIGN REVIEW GATE │
│ (goodtogo:design-review-gate) │
│ │
│ Spawns in parallel: │
│ • Product Manager Agent (use cases) │
│ • Architect Agent (architecture) │
│ • Designer Agent (UX/API) │
│ • Security Design Agent (threats) │
│ • CTO Agent (TDD readiness) │
│ │
│ Iterates until ALL FIVE approve │
└─────────────────────────────────────────┘
│
▼
ALL APPROVED? ────No────► Iterate on design
│
Yes
│
▼
"Ready to set up for implementation?"
This skill auto-activates when:
superpowers:brainstorming completes and commits a design documentdocs/plans/*-design.md is created and committedWhen a design document is committed, this extension:
Detects completion - Monitors for commits to docs/plans/*-design.md
Announces review gate:
## 🔄 Design Review Gate Activated
Your design document has been committed. Before proceeding to implementation,
I'll run it through our review agents to ensure it's ready.
Spawning reviews:
- 📦 Product Manager Agent (use case/requirements validation)
- 🏗️ Architect Agent (technical architecture)
- 🎨 Designer Agent (UX/API design)
- 🔒 Security Design Agent (threat modeling/security review)
- 🔬 CTO Agent (TDD readiness)
This typically takes 2-3 minutes...
Spawns review agents - Uses design-review-gate skill
Aggregates results - Combines feedback from all five agents
Reports outcome:
If APPROVED:
## ✅ Design Review Gate: PASSED
All five reviewers have approved your design!
| Agent | Verdict | Notes |
| --------------- | -------- | ------------------------------------- |
| Product Manager | APPROVED | Clear use cases, measurable benefits |
| Architect | APPROVED | Clean architecture, follows patterns |
| Designer | APPROVED | Good API design, clear error states |
| Security Design | APPROVED | No high-risk threats, mitigations OK |
| CTO | APPROVED | TDD specs present, ready to implement |
### Next Steps
1. Create BEADS epic for this feature
2. Set up worktree for isolated development
3. Begin implementation
Ready to proceed? [Yes / No]
If NEEDS_REVISION:
## ⚠️ Design Review Gate: NEEDS REVISION
Some reviewers found issues that need to be addressed.
### Blocking Issues
#### Architect Agent
- [Issue 1]
- [Issue 2]
#### Security Design Agent
- [Missing rate limits]
#### CTO Agent
- [Missing TDD specs]
### Questions Requiring Answers
- [Question 1]
---
Please revise the design document and I'll re-run the review gate.
(Iteration 1 of 3)
This extension runs AFTER brainstorming completes but BEFORE the "ready for implementation?" prompt.
Delegates the actual review work to the design-review-gate skill.
After approval, can automatically:
For truly simple designs (< 1 day of work), the review gate can be skipped:
User: "This is a simple fix, skip the review gate"
Agent will ask for confirmation before skipping.
Even for non-brainstorming contexts:
User: "/project:review-design docs/plans/2026-01-11-my-design.md"
The extension is working correctly when:
Check:
git log --oneline -5)docs/plans/ with -design.md suffix?Each agent should complete within 2-3 minutes. If longer:
After 3 iterations, the gate will escalate to human decision:
User: "Let's design a new feature for contact tagging"
[brainstorming skill runs...]
[Q&A, design sections, validation...]
Claude: "I've committed the design document to docs/plans/2026-01-11-contact-tagging-design.md"
## 🔄 Design Review Gate Activated
Spawning review agents...
[2 minutes later]
## ✅ Design Review Gate: PASSED
All five reviewers approved! Ready to set up for implementation?
User: "Yes"
Claude: "I'll create a BEADS epic and set up a worktree..."
superpowers:brainstorming - The skill this extendsgoodtogo:design-review-gate - The review gate implementationsuperpowers:writing-plans - Used after approval for detailed plansgoodtogo:beads-orchestration - For creating epics and tracking workMulti-agent orchestration for GitHub Issues using BEADS task tracking
Automatic review gate that runs after brainstorming completes - spawns PM, Architect, Designer, Security, and CTO agents in parallel, iterates until all approve
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently