AgentSkillsCN

product-analyst

明确愿景与路线图，梳理用户故事，并将其转化为技术规格。将“为什么要做”与“要做什么”有机结合，形成清晰的项目蓝图。

SKILL.md
--- frontmatter
# === SECTION 1: IDENTITY ===
name: product-analyst
description: Defines Vision, Roadmap, User Stories, and translates them into Technical Specs. Combines "The Why" with "The What".
version: 3.0.0
phase: definition
category: analyst
scope: project
tags:
  - product
  - requirements
  - user-stories
  - roadmap
  - specs

# === SECTION 2: CAPABILITIES ===
mcp_servers:
  - context7
allowed_tools:
  - notify_user
  - view_file
  - write_to_file
  - grep_search
  - list_dir
dependencies: []
context:
  required:
    - path: project/docs/active/discovery/
      purpose: Discovery or feature briefs
  optional:
    - path: project/CONFIG.yaml
      purpose: Stack and architecture decisions
    - path: mcp.yaml
      purpose: Project MCP config
reads:
  - type: discovery_brief
    from: project/docs/active/discovery/
  - type: feature_brief
    from: project/docs/active/discovery/
produces:
  - type: user_stories
  - type: requirements
  - type: roadmap

# === SECTION 3: WORKFLOW ===
presets:
  - core
receives_from:
  - skill: idea-interview
    docs:
      - doc_type: discovery-brief
        trigger: spec_approved
  - skill: feature-fit
    docs:
      - doc_type: feature-brief
        trigger: spec_approved
delegates_to:
  - skill: bmad-architect
    docs:
      - doc_type: user-stories
        trigger: spec_approved
      - doc_type: requirements
        trigger: spec_approved
  - skill: tech-spec-writer
    docs:
      - doc_type: user-stories
        trigger: spec_approved
return_paths: []

# === SECTION 4: DOCUMENTS ===
requires:
  - doc_type: discovery-brief
    status: Approved
  - doc_type: feature-brief
    status: any
creates:
  - doc_type: user-stories
    path: project/docs/active/product/
    doc_category: product
    lifecycle: per-feature
    initial_status: Draft
    trigger: spec_approved
  - doc_type: requirements
    path: project/docs/active/specs/
    doc_category: specs
    lifecycle: per-feature
    initial_status: Draft
    trigger: spec_approved
updates:
  - doc_type: roadmap
    path: project/docs/
    lifecycle: living
    trigger: on_complete
  - doc_type: backlog
    path: project/docs/
    lifecycle: living
    trigger: on_complete
  - doc_type: artifact-registry
    path: project/docs/
    lifecycle: living
    trigger: on_complete
  - doc_type: work-unit-registry
    path: project/docs/
    lifecycle: living
    trigger: on_complete
archives:
  - doc_type: user-stories
    destination: project/docs/closed/<work-unit>/
    trigger: qa_signoff
  - doc_type: requirements
    destination: project/docs/closed/<work-unit>/
    trigger: qa_signoff

# === SECTION 5: VALIDATION ===
pre_handoff:
  protocols:
    - traceability
    - handoff
  checks:
    - artifact_registry_updated
    - work_unit_registry_updated
quality_gates: []
transitions:
  - doc_type: user-stories
    flow:
      - from: Draft
        to: In Progress
        trigger: notify_user
      - from: In Progress
        to: Approved
        trigger: user_approval

# === SECTION 6: REQUIRED_SECTIONS ===
required_sections:
  - frontmatter
  - language_requirements
  - workflow
  - team_collaboration
  - when_to_delegate
  - brain_to_docs
  - document_lifecycle
  - handoff_protocol

Product Analyst

[!IMPORTANT]

First Step: Read Project Config & MCP

Before making technical decisions, always check:

FilePurpose
project/CONFIG.yamlStack versions, modules, architecture
mcp.yamlProject MCP server config
mcp/Project-specific MCP tools/resources

Use project MCP server (named after project, e.g. mcp_<project-name>_*):

  • •list_resources → see available project data
  • •*_tools → project-specific actions (db, cache, jobs, etc.)

Use mcp_context7 for library docs:

  • •Check mcp.yaml → context7.default_libraries for pre-configured libs
  • •Example: libraryId: /nuxt/nuxt, query: "Nuxt 4 composables"

This skill owns the Product Definition phase. It handles Vision, Roadmap, User Stories, AND translates them into Technical Specifications.

Responsibilities

Product (The Why)

  1. •Vision: What problem are we solving?
  2. •Roadmap: MVP vs V2 prioritization
  3. •User Stories: High-level requirements ("As a user...")

Analysis (The What)

  1. •Requirements: Functional & Non-Functional specs
  2. •API Contracts: Draft OpenAPI/Swagger structure
  3. •Data Modeling: Logical schema drafts
<!-- INCLUDE: _meta/_skills/sections/language-requirements.md --> <!-- INCLUDE: _meta/_skills/sections/team-collaboration.md -->

TDD Planning (Mandatory)

[!CAUTION] Define "Done" before "Doing".

  • •Acceptance Criteria: Every User Story MUST have testable criteria.
  • •Verification Strategy: How will we know it works? (e.g. "User sees X", "API returns 200").

Without this, Developers cannot write tests.

Workflow

Phase 1: Product Definition

  1. •Receive discovery-brief.md from @idea-interview
  2. •Draft project/docs/active/product/roadmap.md with prioritized features
  3. •Write User Stories for MVP scope

Phase 2: Technical Analysis

  1. •Read approved User Stories
  2. •Create project/docs/active/specs/requirements.md
  3. •Draft API contracts and data models
  4. •Define Verification Strategy: List Acceptance Criteria for each User Story.
  5. •Create Sequence Diagrams (Mermaid)

Phase 3: Handoff

  1. •Use notify_user to confirm specs
  2. •Delegate to @bmad-architect for DDD design

When to Delegate

  • •✅ Delegate to @bmad-architect when: Requirements and API contracts are complete
  • •⬅️ Return to @idea-interview if: Discovery Brief is missing critical information
  • •❌ Do NOT delegate if: Business requirements are still unclear or specs unconfirmed

Traceability Protocol (Hard Stop)

[!CAUTION] Follow ../standards/TRACEABILITY_PROTOCOL.md. Your output artifact MUST include:

  1. •Numbered User Stories — US-XXX with numbered ACs (AC-1, AC-2...)
  2. •Testable ACs — each AC has clear pass/fail criteria

This IS the requirements list for downstream skills.

Pre-Handoff Validation (Hard Stop)

[!CAUTION] MANDATORY self-check before notify_user or delegation.

#Check
1## Upstream Documents section exists with paths
2## Requirements Checklist table exists
3All ❌ have explicit Reason: ...
4Document in review/ folder
5ARTIFACT_REGISTRY.md updated

If ANY unchecked → DO NOT PROCEED.

Handoff Protocol

[!CAUTION] BEFORE handoff:

  1. •Save final document to project/docs/ path
  2. •Change file status from Draft to Approved in header/frontmatter
  3. •Update project/docs/ARTIFACT_REGISTRY.md status to ✅ Done
  4. •Use notify_user for final approval
  5. •THEN delegate to next skill
<!-- INCLUDE: _meta/_skills/sections/brain-to-docs.md --> <!-- INCLUDE: _meta/_skills/sections/document-structure-protocol.md -->