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 writing-plansgit 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/writing-plans)<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/writing-plans"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/writing-plans/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/writing-plans"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/writing-plans.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.00050 | $0.00808 |
| Opus 5 | $0.00025 | $0.00404 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
writing-plans 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 12d 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
Writing-Plans(桥接到 superpowers)
Contract
- Inputs: signed design spec, interface/domain model as available
- Outputs:
docs/superpowers/plans/YYYY-MM-DD-<topic>-plan.md - Gates: tasks are independently executable and each is no larger than 2 hours
- Required disciplines:
stage-gate - Next:
/tdd
本仓库不维护此 skill 的内容。完整纪律请读:
<SUPERPOWERS_SKILL_ROOT>/writing-plans/SKILL.md
何时调
- brainstorming / design-an-interface / domain-modeling 之后
- 需要把 spec 拆成可逐步执行的计划
衔接点
- 产出:
docs/superpowers/plans/YYYY-MM-DD-<topic>-plan.md(含 ≤ 2h 子任务列表) - 下一步:
/tdd(开始红绿循环) - 门控:
disciplines/stage-gate第 2 层 + 第 3 层(每个子任务)
降级方案(superpowers 未装时)
如果 <SUPERPOWERS_SKILL_ROOT>/writing-plans/ 不存在,按以下 4 步产出可执行计划:
1. 拆任务(每个 ≤ 2h)
按以下规则拆:
- 可独立运行(一个任务完不依赖另一个任务的产物)
- 可独立验证(每个任务有明确的 PASS 标志)
- 可估时(≤ 2h,超出则继续拆)
- 依赖关系显式(用
Blocked by:标注)
2. 每个任务写 7 件套
| 字段 | 例子 |
|---|---|
| Title | "实现 ASN 收货状态机 10→30" |
| Files | service/AsnReceiveService.java |
| Test | AsnReceiveServiceTest#shouldTransitionFrom10To30 |
| Steps | 1. 写 RED 2. 跑确认失败 3. 写实现 4. GREEN 5. 提交 |
| Verify | mvn test -Dtest=AsnReceiveServiceTest |
| Blocked by | - |
| Estimate | 1.5h |
3. 顺序 + 依赖图
- 第 1 个任务:数据模型 / 状态机先建(后面的都依赖)
- 中间任务:业务逻辑 / 接口契约
- 最后任务:联调 / E2E 测试
4. 输出 + 签字
写到 docs/superpowers/plans/YYYY-MM-DD-<topic>-plan.md,末尾 ## Sign-off 等用户白名单签字(4 句之一)。
最小纪律摘要
- 每个任务 ≤ 2h:超 2h 必须拆(否则 TDD 红绿循环失控)
- 7 件套不能少:缺 Verify = 不知道什么时候算 PASS
- 依赖写显式:不写 = 后续乱序执行
- 第 1 个任务不含集成:先建地基,再在上面盖楼
安装提示
npx skills@latest add obra/superpowers-writing-plans
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.
- 12d ago First seen · 79 lines · 50 tokens per session scan A e7b4df0788e9
writing-plans is a skill published in the GitHub repository BlueprintOS/analysis-to-delivery (26 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 808 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
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.…
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…
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.
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.