doc-brd
仓库创建 2025年11月10日最近提交 20 天前SkillHot 收录 20 天前
▸ 精选理由
适合新项目起始阶段快速形成结构化且标准的BRD。
这个 Skill 做什么
生成业务需求文档,定义目标、范围与成功标准。
把业务目标、范围、关键干系人和验收标准用业务语言整理成一份 BRD,作为新项目或新功能的起点文档。启动产品设计或需求对齐时用它来统一期望并界定 MVP 范围。它是 SDD 流程的第一层,便于后续衔接到 PRD、BDD 和技术规范,降低沟通歧义。
▸ 展开 SKILL.md 英文原文
Create a Business Requirements Document (BRD) - Layer 1 of the SDD flow, defining business needs, objectives, and success criteria. Use when starting a new project or feature.
16
Stars
3
Forks
40
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/main/platforms/claude-code-plugin/skills/doc-brd/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/vladm3105/aidoc-flow-framework/main/platforms/claude-code-plugin/skills/doc-brd/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# doc-brd ## Purpose Create a **Business Requirements Document (BRD)** — Layer 1 of the SDD flow. A BRD captures business objectives, stakeholders, scope, and success criteria in business language, before any product or technical detail. **Layer**: 1 (entry point, no upstream). **Downstream**: PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code. One BRD = one MVP iteration (5–15 focused requirements). New features get a new BRD; link cycles with `@depends: BRD-NN`. ## When to Use Use `doc-brd` when: - Starting a new project or feature and defining business requirements. - Documenting strategic alignment, market context, and success criteria. - Translating an implementation plan back in
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有