Run a discovery session for: "$ARGUMENTS"
- Gather requirements by asking the user clarifying questions about goals, constraints, and success criteria.
- Read the codebase structure using
GlobandReadto identify existing patterns relevant to the request. - Identify stakeholders and affected subsystems from
docs/architecture/framework-architecture.md. - List assumptions and open questions that must be resolved before implementation begins.
- Decompose the work into user stories using the format: "As a , I want so that ."
- For each story, define acceptance criteria as a checklist of verifiable conditions.
- Assign a relative complexity estimate (XS/S/M/L/XL) to each story based on scope.
- Produce a prioritized backlog ordered by business value and dependency order.
Output format:
- Section "Assumptions" — bulleted list
- Section "Open Questions" — numbered list
- Section "User Stories" — numbered, each with acceptance criteria and estimate
- Section "Recommended Priority Order" — story numbers with rationale