AgentSkillsCN

product-management

以战略思维驱动产品规划、优先级排序与商业价值创造。倾听客户需求,明确产品范围,凝聚各方利益相关者共识。既可独立运行,也可与“邪恶团队”深度集成。 适用场景如下:“产品战略”、“需求分析”、“用户故事”、“我们该开发什么?”、“功能优先级排序”、“范围界定”

SKILL.md
--- frontmatter
name: product-management
description: |
  Strategic product thinking for roadmap, priorities, and business value.
  Elicit requirements, define scope, and align stakeholders.
  Works standalone or integrated with wicked-crew.

  Use when: "product strategy", "requirements", "user stories",
  "what should we build", "prioritize features", "scope definition"

Product Management Skill

Bridge customer needs with delivery execution through structured product thinking.

Core Concept

Product management is clarity. Transform vague ideas into actionable requirements with clear acceptance criteria and aligned stakeholders.

Three Key Activities

ActivityWhenOutput
ElicitEarly clarifyRequirements, user stories, scope
AcceptancePost-designAcceptance criteria, test scenarios
AlignThroughoutStakeholder consensus, trade-offs

Commands

CommandPurpose
/wicked-product:elicitRequirements elicitation
/wicked-product:acceptanceDefine acceptance criteria
/wicked-product:alignStakeholder alignment

Usage

bash
# Elicit requirements from brief
/wicked-product:elicit outcome.md

# Define acceptance criteria from design
/wicked-product:acceptance phases/design/

# Facilitate stakeholder alignment
/wicked-product:align --stakeholders "eng,qe,ops"

Elicitation Process

  1. Understand Context: Read available materials
  2. Ask Questions: Surface gaps and ambiguities
  3. Write Stories: As a [persona], I want [capability], so that [benefit]
  4. Define Criteria: Given/When/Then scenarios
  5. Validate: Check completeness and testability

Output Artifacts

Elicitation produces:

  • User Stories: Persona + capability + benefit
  • Acceptance Criteria: Testable scenarios
  • Open Questions: Ambiguities to resolve
  • Kanban Updates: Traceability

Quality Checks

Good requirements are:

  • Clear: No ambiguity
  • Testable: Can verify completion
  • Valuable: Clear benefit stated
  • Independent: Standalone value
  • Small: Completable in iteration

Integration

Works with:

  • wicked-crew: Auto-triggered during clarify phase
  • wicked-kanban: Stores requirements and acceptance criteria
  • wicked-qe: Acceptance criteria feed test scenarios
  • wicked-mem: Cross-project requirements patterns

Example Flow

code
User: "We need a login feature"

Product: Eliciting requirements...

US1: User Authentication
As a customer
I want to log in with email and password
So that I can access my account securely

Acceptance Criteria:
1. Given valid credentials, When I submit login, Then I access my dashboard
2. Given invalid password, When I submit login, Then I see error message
3. Given account locked, When I submit login, Then I see lockout message

Open Questions:
- Password reset flow?
- Social login support?
- Session timeout duration?

External Integration Discovery

Product management can leverage available integrations by capability:

CapabilityDiscovery PatternsProvides
Analyticsposthog, mixpanel, amplitudeUser behavior data
Project managementjira, linear, githubExisting tickets/context
Customer feedbackzendesk, intercomSupport ticket insights

Run ListMcpResourcesTool to discover available integrations. Use wicked-kanban when no project management MCP available.

Progressive Disclosure

  • SKILL.md (this file): Overview and quick start
  • refs/user-story-template.md: Detailed story format
  • refs/acceptance-criteria-guide.md: Writing testable criteria