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 to-brdgit 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/to-brd)<a href="https://agentmods.dev/skills/blueprintos/analysis-to-delivery/to-brd"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/to-brd/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/to-brd"><img src="https://agentmods.dev/badge/skills/blueprintos/analysis-to-delivery/to-brd.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.00064 | $0.01072 |
| Opus 5 | $0.00032 | $0.00536 |
| Sonnet 5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
to-brd 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 10d 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
To-BRD — 业务需求文档生成
Contract
- 输入: 已签字的
TASK_CONFIRM_*.md、REVIEW_需求确认书.md、REVIEW_字段对齐分析.md、paths/knowledge-path.md - 输出:
01-业务需求文档 BRD.md、ASCII 流程图、可选业务流程图.drawio - 门控: BRD 必备章节齐全;字段映射与知识库核对;用户签字
- Required rules:
stage-gate,no-field-guessing,ascii-flowchart,doc-numbering,goal-boundary - Required paths:
knowledge-path,doc-naming-path - 下一步:
/compliance-review
适用场景
- TASK_CONFIRM 和字段对齐分析已通过
- 需要把业务需求整理成 BRD 交给团队评审
- 需要画业务流程图 / 状态流转图
流程步骤
1. 加载模板
templates/BRD.md(9 节必备章节)
2. 填充内容
按 BRD 模板逐节生成:
| 章节 | 内容来源 |
|---|---|
| 一、项目概述 | TASK_CONFIRM §1-3 |
| 二、角色与职责 | 业务调研 |
| 三、业务流程 | ASCII 流程图 / drawio |
| 四、功能模块 | TASK_CONFIRM §功能描述 |
| 五、数据要求 | 字段对齐分析 + 知识库 |
| 六、合规要点 | 预留,阶段 4 填 |
| 七、非功能需求 | 性能/可靠性/安全/可维护性 |
| 八、风险与约束 | 团队约束 + 外部依赖 |
| 九、上线计划 | 团队节奏 |
3. 画流程图
- 状态流转图:ASCII(参考
rules/ascii-flowchart.md) - 业务流程图:简单用 ASCII,复杂用 drawio
- 泳道图:ASCII(角色分工清晰)
4. 字段映射表
把字段对齐分析里的 ✅ 项固化到 BRD §五.3:
| 业务概念 | 字段 | 备注 |
|---|---|---|
| ASN 单号 | ASN.TC_ASN_ID |
❌ 严禁用 ASN_NBR |
5. DB 验证(如涉及)
- 仅允许
SELECT查询 - 用
desc table_name验证字段定义 - 严禁 任何 DDL/DML 写操作
输出
01-业务需求文档 BRD.md业务流程图-状态流转.txt(ASCII)业务流程图-收货流程.txt(如需要,泳道图)业务流程图.drawio(可选,用于可视化)
调用的 rule
rules/ascii-flowchart— 流程图规范rules/no-field-guessing— 字段名必须查知识库rules/doc-numbering— 文档编号 01
结束条件
- BRD 9 个必备章节齐
- ASCII 流程图 + 状态流转图
- 字段映射表通过
field-alignment-check.py - 用户签字进入阶段 4
反模式
- ❌ 用 Mermaid 写流程图 — 必须 ASCII(参考 rules/ascii-flowchart.md);可视化交付经
flow-to-mermaid.py --ascii-strict - ❌ 泳道图回流箭头散乱 — 必须汇聚到同一目标节点(回流闭环强制)
- ❌ 字段映射表缺知识库来源 — 每条字段必须标"WMOS 知识库/XX 章"或"项目侧 schema"
- ❌ 9 章节缺一 —
brd-check.py --strict必须 exit 0 - ❌ 写完不跑
field-alignment-check.py— 应在签字前自动跑一遍,errors=0 才签字 - ❌ 流程图用真实人名/客户名 — 用角色占位(仓管员/客户/系统)
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.
- 10d ago First seen · 97 lines · 64 tokens per session scan A cc4d651fa63a
to-brd is a skill published in the GitHub repository BlueprintOS/analysis-to-delivery (26 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,072 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…
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…
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.…
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…
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.