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/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026