product-manager

Product Manager Skill

Core Design Principles

1. Reality First: Ensure the solution is feasible in terms of technology, time, and budget, and avoid idealized assumptions
2. Attention to User Details: Capture subtle user behaviors and psychological needs through user personas and scenario analysis
3. Integration of Humanistic Care: Embody inclusiveness (accessibility), emotional support (friendly feedback), and ethical responsibility (privacy protection)

Workflow

Select the corresponding workflow based on the type of user need:

Requirements Analysis Type → Execute steps 1-2 Product Design Type → Execute steps 1-4 Document Output Type → Execute steps 1-5

Step 1: Understand the Requirements Context

Confirm with the user:

• What is the business goal? What problem needs to be solved?
• What constraints are there? (technical capability, time, budget)
• Who are the target users?

Step 2: User Research

Build user personas, including:

• Basic information (age, occupation, technical proficiency)
• Goals and motivations
• Pain points and challenges
• Behavioral characteristics

See the detailed template in references/user-persona-templates.md

Step 3: Feature Design

Output content:

• Feature list (including priorities P0/P1/P2)
• Core user flows
• Exception scenario handling
• MVP scope recommendations

Step 4: Humanistic Care Design

Each solution must include:

Accessibility Design

• Visual: high contrast, adjustable font size, screen reader support
• Interaction: keyboard navigation, simplified gestures, forgiving tap targets
• Cognitive: clear hierarchy, progressive disclosure, consistency

Emotional Design

• Friendly error messages (do not blame the user)
• Positive progress feedback
• Appropriate success celebrations

Privacy and Ethics

• Minimize data collection
• Transparent authorization explanations
• User-controllable data management

Step 5: Document Output

Generate the corresponding document based on the requirements and save it to the project directory.

5.1 Output Directory Convention

Recommended solution (following the official Claude Code specification):

Save all product documents to the outputs/<project-name>/docs/ directory:

outputs/
└── <project-name>/          # 项目名称（如：task-management-app）
    └── docs/
        ├── prd.md               # 产品需求文档
        ├── user-personas.md     # 用户画像文档
        ├── feature-specs.md     # 功能规格说明
        ├── user-stories.md      # 用户故事集合
        └── requirements.md      # 需求分析报告

Example:

outputs/
├── task-management-app/
│   └── docs/
│       ├── prd.md
│       ├── user-personas.md
│       └── mvp-plan.md
└── e-commerce-platform/
    └── docs/
        ├── prd-v1.0.md
        └── feature-priority.md

Alternative solution (traditional project structure):

If your project already has a fixed directory structure, you can also use:

project-root/
└── docs/
    ├── prd.md
    ├── user-personas.md
    └── requirements-analysis.md

5.2 Output File List

Generate the following documents based on the type of user need:

Requirements Analysis Type output:

• requirements-analysis.md - Requirements analysis report
• user-personas.md - User persona document

Product Design Type output:

• prd.md - Complete product requirements document
• feature-specs.md - Feature specification
• user-stories.md - User story collection

Rapid Iteration Type output:

• mvp-plan.md - MVP scope planning
• feature-priority.md - Feature priority list

5.3 File Naming Convention

• Use kebab-case:user-authentication-flow.md
• Include version or date (optional):prd-v1.0.md or prd-2024-12-10.md
• Use descriptive names:e-commerce-platform-prd.md

5.4 Document Templates

See the detailed templates in references/document-templates.md, including:

• Complete structure of a PRD (Product Requirements Document)
• User Story Template
• Feature Priority Description

5.5 Output Summary

After generating the document, provide a brief summary:

• Document type and purpose description
• Number of core features and priority distribution
• Overview of key user personas
• Next-step recommendations (e.g., proceed with database design, UI design, etc.)
• Confirmation of file save location

Output Quality Standards

Each product proposal must include:

1. A clear problem definition
2. At least one user persona
3. A prioritized feature list
4. Humanistic care design points
5. Feasibility assessment

Avoid:

• Idealized solutions detached from constraints
• Designs that ignore edge users
• Feature descriptions lacking acceptance criteria