/workflow-requirements - Requirements to Stories Workflow

Start the Requirements to Stories workflow to analyze a feature request and create well-defined user stories. Coordinates Business Analyst, Product Owner, Architect, and QA Engineer.

Arguments: $ARGUMENTS - Feature description or epic key

Usage

/workflow-requirements <description>
/workflow-requirements PROJ-100

Examples

/workflow-requirements "User authentication with social login"
/workflow-requirements "Add dark mode support to the application"
/workflow-requirements PROJ-100

What It Does

Executes the requirements to stories workflow:

1. Orchestrator - Receives feature request
2. Business Analyst - Analyzes requirements, asks clarifying questions
3. Product Owner - Validates stories, sets priorities (MoSCoW)
4. Software Architect - Reviews technical feasibility, identifies dependencies
5. QA Engineer - Reviews testability, suggests test scenarios
6. Orchestrator - Finalizes stories, documents in Jira

Outputs

• User stories in Jira with:
  • Clear acceptance criteria
  • Story point estimates
  • Priority (MoSCoW)
  • Dependencies identified
• Business Requirements Document (BRD) in Confluence
• Technical notes from Architect

Workflow File

Loads from: workflows/requirements-to-stories.md

Related Commands

• /story - Quick single story creation (skips full analysis)
• /workflow-sprint - Plan sprint with created stories
• /workflow-design - Design UI for created stories