Stats
Actions
Tags
From wicked-garden
Elicits structured user stories with acceptance criteria from vague ideas or stakeholder asks, following INVEST quality criteria and producing prioritized output with open questions.
How this command is triggered — by the user, by Claude, or both
Slash command
/wicked-garden:elicitproduct/The summary Claude sees in its command listing — used to decide when to auto-load this command
# /wicked-garden:product:elicit
Elicit requirements and write user stories with acceptance criteria.
## Run it inline (no dispatch)
1. Read context: the target document(s) (`outcome.md`, brief, `docs/requirements/`), or accept `--interactive`. Honor `--personas` and `--scope`.
2. `Read("${CLAUDE_PLUGIN_ROOT}/skills/product/refs/elicit.md")` — the process, INVEST quality criteria, completeness check, traceability, and output format.
3. Apply the rubric directly and emit user stories (priority + complexity + dependencies + AC) and open questions.
For complexity >= 3 or compliance projects...Elicit requirements and write user stories with acceptance criteria.
outcome.md, brief, docs/requirements/), or accept --interactive. Honor --personas and --scope.Read("${CLAUDE_PLUGIN_ROOT}/skills/product/refs/elicit.md") — the process, INVEST quality criteria, completeness check, traceability, and output format.For complexity >= 3 or compliance projects, produce a requirements graph instead — load the requirements-analysis / requirements-graph skills. Persist on the active clarify task via TaskUpdate.
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-garden