Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BlueprintOS/analysis-to-delivery --skill brainstorminggit clone --depth 1 https://github.com/BlueprintOS/analysis-to-deliveryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/blueprintos/analysis-to-delivery/brainstorming)<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/brainstorming"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/brainstorming/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/brainstorming"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/brainstorming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00054 | $0.00927 |
| Opus 5 | $0.00027 | $0.00464 |
| Sonnet 5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
brainstorming scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Brainstorming(桥接到 superpowers)
Contract
- Inputs: feature idea, user constraints, optional signed analysis-delivery docs
- Outputs:
docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md - Gates: user agrees the design captures intent
- Required disciplines:
stage-gate - Next:
/design-an-interfaceor/writing-plans
本仓库不维护此 skill 的内容。完整纪律请读:
<SUPERPOWERS_SKILL_ROOT>/brainstorming/SKILL.md
何时调
- 拿到新需求/新功能,需要先与用户对齐
- 在
analysis-delivery-workflow阶段 2(grill-task)之后 - 在
dev-design阶段 7 之前
如何调
# 方式 1:直接调 superpowers 官方
/brainstorming
衔接点
- 产出:
docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md - 下一步:
/writing-plans(拆任务) - 门控:
disciplines/stage-gate第 2 层
🚧 桥接层不重复 superpowers 内容,保持单一权威源。
降级方案(superpowers 未装时)
如果 <SUPERPOWERS_SKILL_ROOT>/brainstorming/ 不存在,按以下 4 步在本仓库独立完成脑暴:
1. 5 问澄清
逐一问用户以下 5 个问题,一次一个问题,不堆叠:
| # | 提问 | 目标 |
|---|---|---|
| 1 | 这个功能给谁用?(角色 / 使用场景) | 锁定用户 |
| 2 | 解决他们什么具体问题? | 锁定价值 |
| 3 | 不做会怎样?(现状如何) | 锁定紧迫性 |
| 4 | 成功长什么样?(可观测的产物) | 锁定验收标准 |
| 5 | 范围边界?哪些场景不做? | 锁定非目标 |
任何问题用户答"不知道" → 拆子问题再问,禁止替用户编答案。
2. 3 候选设计
基于澄清结果,生成 3 个候选方案,每个含:
- 核心思路(1-2 句)
- 关键数据结构 / 接口(粗略)
- 影响范围(哪些文件/模块要改)
- 取舍(选 A 牺牲了什么 / 得到了什么)
3. 用户选 1 + 反馈循环
把 3 个候选展示给用户 → 用户选 1 → 允许其修改细节 → 输出设计稿到 docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md。
4. 签字闭环
设计稿末尾加 ## Sign-off,等用户白名单话术(4 句之一)签字:
- "我已全部确认,可以进入下一步"
- "确认通过"
- "全部完成,继续"
- "approved, proceed to next stage"
❌ "OK/好/继续" 一律不视为签字。
最小纪律摘要(脑暴专用)
- 一次一问:堆叠问题 = 用户答不全
- 3 候选而非 1:多视角避免单点盲区
- 写下来不靠记忆:产出 design.md 是脑暴的唯一交付物
- 签字才能进下一阶段
安装提示
npx skills@latest add obra/superpowers-brainstorming
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 96 lines · 54 tokens per session scan A b6ad49521c93
brainstorming is a skill published in the GitHub repository BlueprintOS/analysis-to-delivery (26 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 927 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.