Agent Skills › bacoco/BMad-Skills › bmad-product-planning

bmad-product-planning

GitHub

用于将已验证的发现洞察转化为生产就绪的产品需求文档（PRD）和史诗路线图，对齐干系人并准备下游架构与交付工作。

.claude/skills/bmad-product-planning/SKILL.md bacoco/BMad-Skills

Trigger Scenarios

用户要求创建 PRD 或产品需求用户希望规划功能或构建项目提及 epic 路线图或结构化计划

Install

npx skills add bacoco/BMad-Skills --skill bmad-product-planning -g -y

More Options

Non-standard path

npx skills add https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/bmad-product-planning -g -y

Use without installing

npx skills use bacoco/BMad-Skills@bmad-product-planning

指定 Agent (Claude Code)

npx skills add bacoco/BMad-Skills --skill bmad-product-planning -a claude-code -g -y

安装 repo 全部 skill

npx skills add bacoco/BMad-Skills --all -g -y

预览 repo 内 skill

npx skills add bacoco/BMad-Skills --list

SKILL.md

Frontmatter

{
    "name": "bmad-product-planning",
    "metadata": {
        "outputs": [
            "product-requirements-document",
            "feature-specs",
            "epic-breakdown"
        ],
        "triggers": {
            "keywords": [
                "PRD",
                "requirements",
                "plan",
                "build",
                "feature",
                "epic",
                "roadmap",
                "product"
            ],
            "patterns": [
                "create a PRD",
                "I want to build",
                "plan this feature",
                "write requirements",
                "product document"
            ]
        },
        "auto-invoke": true,
        "capabilities": [
            "prd-creation",
            "requirements-gathering",
            "feature-planning",
            "roadmap-design"
        ],
        "prerequisites": [
            "discovery-brief"
        ]
    },
    "description": "Creates PRDs and plans features.",
    "allowed-tools": [
        "Read",
        "Write",
        "Grep"
    ]
}

Product Requirements Skill

When to Invoke

Automatically activate this skill when the user:

Says "I want to build...", "Let's build...", "Create a..."
Asks "Create a PRD", "Write requirements", "Plan this feature"
Mentions "product requirements", "PRD", "epic roadmap"
Has completed discovery phase and needs formal requirements
Is starting a Level 2-4 project requiring structured planning
Uses words like: build, create, PRD, requirements, plan, feature, product

Specific trigger phrases:

"I want to build [something]"
"Create a PRD for [project]"
"Plan this feature"
"Write the requirements"
"What should be in the PRD?"
"Break this into epics"
"Product requirements for [project]"

Prerequisites check:

If Level 3-4 project: verify analysis phase complete (discovery brief exists)
If missing analysis: recommend invoking bmad-discovery-research first
If Level 0-1: suggest OpenSpec workflow instead

Do NOT invoke when:

User is still exploring/brainstorming (use bmad-discovery-research first)
User is ready for architecture (use bmad-architecture-design instead)
User wants to code directly (check if prerequisites exist first)
Project is Level 0-1 simple change (use OpenSpec)

Mission

Transform validated discovery insights into a production-ready Product Requirements Document (PRD) and epic roadmap that align stakeholders and prepare downstream architecture, UX, and delivery work.

Inputs Required

business_goal: clear outcome statement tied to measurable success metrics
stakeholders: decision makers plus their approvals or open concerns
constraints: technical, regulatory, financial, or timeline guardrails
discovery_artifacts: briefs, research memos, or notes from the discovery-analysis skill

If any input is missing or stale, pause and request the exact artifact before proceeding.

Outputs

Produce two markdown artifacts aligned to the templates in assets/:

PRD.md populated from assets/prd-template.md.template
epics.md populated from assets/epic-roadmap-template.md.template

Deliverables must be written to the project documentation folder (default docs/) and summarized for the requestor.

Process

Validate readiness using the gate in CHECKLIST.md.
Review discovery inputs and clarify remaining unknowns.
Map goals, scope, and constraints into structured PRD sections.
Prioritize epics, sequencing, and acceptance signals for delivery.
Run scripts/generate_prd.py when structured data exists; otherwise compose outputs manually following templates.
Apply the quality checklist before returning deliverables and recommended next steps.

Quality Gates

Confirm every item in CHECKLIST.md is satisfied before delivering the PRD package. Stop and fix any unmet criteria.

Error Handling

If prerequisites are missing or contradictions surface:

Identify which required input is absent and why it blocks progress.
Provide a minimal list of follow-up questions or stakeholders needed.
Recommend re-engaging the discovery-analysis skill or orchestrator when scope is unclear.