npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenproduct/# /wicked-garden:product:elicit Elicit requirements and write user stories with acceptance criteria. ## Usage ## Parameters - **target** (required): Path to document(s) or "--interactive" - **--personas**: Comma-separated list of user personas - **--scope**: Focus area (e.g., "authentication", "data-management") - **--output**: Where to save results (default: console + native task) ## Process 1. **Read Context**: Parse target documents or accept interactive mode 2. **Dispatch to Requirements Analyst**: Elicit requirements, identify gaps, generate user stories 3. **Present Results**:...
/elicitInteractive elicitation method selection and execution. Provides structured reasoning techniques from the curated 24-method registry. Methods include Tree of Thoughts, Pre-mortem Analysis, Red Team vs Blue Team, 5 Whys Deep Dive, and more. <example> user: "/rune:elicit" assistant: "The Tarnished consults the elicitation grimoire..." </example> <example> user: "/rune:elicit --method 11" assistant: "Applying Tree of Thoughts to current context..." </example> <example> user: "/rune:elicit --phase plan:0" assistant: "Showing methods available for planning brainstorm phase..." </example>
/elicitRun a focused interrogation on existing documentation to find ambiguities, contradictions, missing boundaries, and hidden assumptions.
Elicit requirements and write user stories with acceptance criteria.
# Elicit from outcome document
/wicked-garden:product:elicit outcome.md
# Elicit from project brief
/wicked-garden:product:elicit phases/clarify/brief.md
# Elicit from directory of documents
/wicked-garden:product:elicit docs/requirements/
# Interactive elicitation
/wicked-garden:product:elicit --interactive
Read target document(s) or accept interactive mode parameters:
--personas: Comma-separated list of user personas--scope: Focus area--interactive: Interactive clarification modeTask(
subagent_type="wicked-garden:product:requirements-analyst",
prompt="""Elicit requirements from the following context.
## Context
{target document content OR interactive parameters}
## Parameters
- Personas: {specified personas or infer from context}
- Scope: {focus area if specified}
- Mode: {interactive or document-based}
## Task
1. **Identify Gaps**: What information is missing or unclear?
2. **Ask Questions**: Surface questions requiring stakeholder input
3. **Write User Stories**: Follow the format:
- As a {persona}
- I want {capability}
- So that {benefit}
4. **Assign Priority**: P0 (must-have/launch blocker), P1 (important/near-term), P2 (nice-to-have/deferrable) for each story
5. **Assign Complexity**: S (hours), M (1-2 days), L (3-5 days), XL (week+) for each story
6. **Define Dependencies**: List formal story-to-story or system dependencies for each story (use story IDs or component names)
7. **Define Acceptance Criteria**: Given/When/Then format for each story
8. **Provide Recommendations**: Next steps for requirements refinement
## Return Format
Provide:
- User Stories count
- Acceptance Criteria count
- Open Questions count
- Individual user stories with priority, complexity, dependencies, and AC
- Open questions list
- Recommendations
"""
)
Format the agent's output into the standard elicitation report structure.
## Requirements Elicitation Results
### User Stories Defined: {count}
### Acceptance Criteria: {count}
### Open Questions: {count}
---
### US1: {Story Title}
**As a** {persona}
**I want** {capability}
**So that** {benefit}
**Priority**: P0 | P1 | P2
**Complexity**: S | M | L | XL
**Dependencies**: {story IDs or system components this story depends on, or "None"}
**Acceptance Criteria**:
1. Given {context}, When {action}, Then {outcome}
---
### Open Questions
1. {Question requiring stakeholder input}
### Recommendations
- {Next step}
Automatically updates:
[product:requirements:elicited:success]$ /wicked-garden:product:elicit outcome.md
Reading outcome.md...
[Dispatches to requirements-analyst agent]
[Agent analyzes requirements and generates user stories]
User Stories Defined: 5
Open Questions: 2
US1: User Login
As a customer
I want to log in with email/password
So that I can access my account
AC1: Given valid credentials, When I submit, Then I access dashboard
AC2: Given invalid password, When I submit, Then I see error
Open Questions:
1. Password complexity requirements?
2. Social login support (Google, GitHub)?
Stored on active task: task-001
Event emitted: [product:requirements:elicited:success]