mikeparcewski/product-management
skills/product/product-management/SKILL.md
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: planning a roadmap, prioritizing a backlog, or defining scope and stakeholder alignment for an upcoming feature.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden product-managementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 8, 2026, 5:52 AM131.5s4 files scanned
SKILL.md
- name:
- product-management
- description:
- |
- Use when:
- planning a roadmap, prioritizing a backlog, or defining scope and
- phase_relevance:
- ["clarify", "design", "review"]
- archetype_relevance:
- ["*"]
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
| Activity | When | Output | |----------|------|--------| | Elicit | Early clarify | Requirements, user stories, scope | | Acceptance | Post-design | Acceptance criteria, test scenarios | | Align | Throughout | Stakeholder consensus, trade-offs |
Commands
| Command | Purpose |
|---------|---------|
| /wicked-garden:product:elicit | Requirements elicitation |
| /wicked-garden:product:acceptance | Define acceptance criteria |
| /wicked-garden:product:align | Stakeholder alignment |
Usage
# Elicit requirements from brief
/wicked-garden:product:elicit outcome.md
# Define acceptance criteria from design
/wicked-garden:product:acceptance phases/design/
# Facilitate stakeholder alignment
/wicked-garden:product:align --stakeholders "eng,qe,ops"
Elicitation Process
- Understand Context: Read available materials
- Ask Questions: Surface gaps and ambiguities
- Write Stories: As a [persona], I want [capability], so that [benefit]
- Define Criteria: Given/When/Then scenarios
- Validate: Check completeness and testability
Output Artifacts
Elicitation produces:
- User Stories: Persona + capability + benefit
- Acceptance Criteria: Testable scenarios
- Open Questions: Ambiguities to resolve
- Task Updates: Traceability via TaskUpdate on the active clarify task
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
- Native tasks: Stores requirements and acceptance criteria via TaskCreate/TaskUpdate with
metadata={event_type:"task", chain_id:"{project}.clarify", source_agent:"requirements-analyst", phase:"clarify"} - qe: Acceptance criteria feed test scenarios
- wicked-brain:memory: Cross-project requirements patterns
Example Flow
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:
| Capability | Discovery Patterns | Provides |
|------------|-------------------|----------|
| Analytics | posthog, mixpanel, amplitude | User behavior data |
| Project management | jira, linear, github | Existing tickets/context |
| Customer feedback | zendesk, intercom | Support ticket insights |
Discover available integrations via capability detection. Use native TaskCreate/TaskUpdate when no project management integration is available.
Progressive Disclosure
- SKILL.md (this file): Overview and quick start
- refs/user-story-template.md: Detailed story format
- refs/acceptance-criteria-guide-fundamentals.md: Writing testable criteria
- refs/acceptance-criteria-guide-examples.md: Domain-specific examples and integration
Related Skills
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/wicked-garden:archetype
tools
VerifiedTrustedCommunity
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
8SKILL.mdUpdated May 8, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026