From wicked-garden
Deep requirements elicitation and user story definition. Transform vague ideas into clear, testable specifications. Use when: "write user stories", "define requirements", "elicit requirements", "clarify scope", "specification document"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Structured requirements elicitation from discovery through documentation.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Structured requirements elicitation from discovery through documentation.
Default: Graph mode. For complexity >= 3 or compliance projects, produce a
requirements/graph (seerequirements-graphskill) instead of a monolithic document. Use--monolithto force the legacy single-file format. See:requirements-graph/SKILL.mdfor graph layout and schema. See:requirements-navigate/SKILL.mdfor querying and maintaining the graph.
Ask the 5 W's:
Format: As a [persona], I want [capability], so that [benefit]
Quality criteria:
For each story:
Given [context/precondition]
When [action/event]
Then [expected outcome]
Include:
Check:
### US{N}: {Story Title}
**As a** {specific persona}
**I want** {specific capability}
**So that** {specific benefit}
**Priority**: {P0/P1/P2}
**Complexity**: {S/M/L/XL}
**Acceptance Criteria**:
1. Given {context}, When {action}, Then {outcome}
2. Given {error condition}, When {action}, Then {error handling}
3. Given {edge case}, When {action}, Then {graceful handling}
**Non-Functional**:
- Performance: {requirement}
- Security: {requirement}
- Usability: {requirement}
**Dependencies**: {Other stories or systems}
**Assumptions**: {What we're assuming}
**Open Questions**: {What needs clarification}
CRUD Operations:
Authentication/Authorization:
Data Validation:
# Search for similar requirements
/wicked-garden:search:docs "user story" --context requirements
# Store requirements on the active clarify task via native TaskUpdate
# TaskUpdate(taskId="{task_id}", description="{previous}\n\n## Requirements\n{user_stories}")
# Recall past patterns
/wicked-garden:mem:recall "requirements for {feature_type}"
See: refs/requirements-output-format-template.md, refs/requirements-example-auth.md, and refs/requirements-example-export-integration.md