Guides end-to-end product development: analyzes requirements, builds user personas and stories, designs features and interactions, writes PRDs, assesses feasibility.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-workflow-agents:product-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **实际情况优先**:确保方案在技术、时间、预算上可行,避免理想化假设
根据用户需求类型选择对应流程:
需求分析类 → 执行步骤 1-2 产品设计类 → 执行步骤 1-4 文档输出类 → 执行步骤 1-5
向用户确认:
构建用户画像,包含:
详细模板见 references/user-persona-templates.md
输出内容:
每个方案必须包含:
无障碍设计
情感化设计
隐私与伦理
根据需求生成对应文档,并保存到项目目录。
推荐方案(遵循 Claude Code 官方规范):
所有产品文档保存到 outputs/<project-name>/docs/ 目录:
outputs/
└── <project-name>/ # 项目名称(如:task-management-app)
└── docs/
├── prd.md # 产品需求文档
├── user-personas.md # 用户画像文档
├── feature-specs.md # 功能规格说明
├── user-stories.md # 用户故事集合
└── requirements.md # 需求分析报告
示例:
outputs/
├── task-management-app/
│ └── docs/
│ ├── prd.md
│ ├── user-personas.md
│ └── mvp-plan.md
└── e-commerce-platform/
└── docs/
├── prd-v1.0.md
└── feature-priority.md
替代方案(传统项目结构):
如果你的项目已有固定目录结构,也可以使用:
project-root/
└── docs/
├── prd.md
├── user-personas.md
└── requirements-analysis.md
根据用户需求类型,生成以下文档:
需求分析类输出:
requirements-analysis.md - 需求分析报告user-personas.md - 用户画像文档产品设计类输出:
prd.md - 完整产品需求文档feature-specs.md - 功能规格说明user-stories.md - 用户故事集合快速迭代类输出:
mvp-plan.md - MVP 范围规划feature-priority.md - 功能优先级列表user-authentication-flow.mdprd-v1.0.md 或 prd-2024-12-10.mde-commerce-platform-prd.md详细模板见 references/document-templates.md,包括:
生成文档后,提供简要总结:
每个产品方案必须包含:
避免:
npx claudepluginhub shining319/claude-code-single-person-workflow --plugin product-workflow-agentsAnalyzes product requirements, builds user personas, designs features with priorities and MVP scope, writes PRDs and specs, assesses feasibility. Outputs docs to outputs/<project>/docs/ with accessibility and privacy focus.
Generates a complete engineering-ready PRD with problem statement, user personas, MoSCoW features, success metrics, and implementation timeline.
Guides product solution design, PRD writing, requirement clarification, feature planning, and trade-off analysis. Walks through complexity assessment, gating checks, and structured outputs, and avoiding technical overreach.