Initial commit
This commit is contained in:
108
commands/create-story.md
Normal file
108
commands/create-story.md
Normal file
@@ -0,0 +1,108 @@
|
||||
---
|
||||
description: Create an AI-ready user story from natural language requirements
|
||||
---
|
||||
|
||||
# Create Story Command
|
||||
|
||||
Generate a well-structured, AI-ready user story from natural language requirements.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/create-story [requirements]
|
||||
```
|
||||
|
||||
## Parameters
|
||||
|
||||
**requirements** (required)
|
||||
- Natural language description of what you need
|
||||
- Can be a feature request, conversation transcript, or rough notes
|
||||
- Include as much context as possible
|
||||
|
||||
**--project** (optional)
|
||||
- Jira project key to create story in
|
||||
- Example: `--project PROJ`
|
||||
|
||||
**--type** (optional)
|
||||
- Story type: feature, bug, technical, spike
|
||||
- Default: feature
|
||||
|
||||
## Examples
|
||||
|
||||
```bash
|
||||
# Create from feature request
|
||||
/create-story Users need to export their dashboard data to PDF for sharing with stakeholders
|
||||
|
||||
# Create with project specified
|
||||
/create-story --project HR Users need password reset functionality
|
||||
|
||||
# Create technical story
|
||||
/create-story --type technical We need to migrate from MySQL to PostgreSQL for better JSON support
|
||||
|
||||
# Create bug fix story
|
||||
/create-story --type bug The export button doesn't work when there's no data in the dashboard
|
||||
```
|
||||
|
||||
## What This Command Does
|
||||
|
||||
1. **Parses Requirements**
|
||||
- Extracts user persona
|
||||
- Identifies capability needed
|
||||
- Determines business value
|
||||
- Notes any constraints
|
||||
|
||||
2. **Generates Story**
|
||||
- Creates structured user story
|
||||
- Follows "As a... I want... So that..." format
|
||||
- Adds context and technical approach
|
||||
|
||||
3. **Creates Acceptance Criteria**
|
||||
- Generates Given/When/Then scenarios
|
||||
- Covers happy path, edge cases, errors
|
||||
- Ensures testability
|
||||
|
||||
4. **Validates Readiness**
|
||||
- Checks against Definition of Ready
|
||||
- Scores on 7 criteria
|
||||
- Provides improvement suggestions
|
||||
|
||||
5. **Offers Jira Creation**
|
||||
- Option to create in Jira
|
||||
- Links acceptance criteria
|
||||
- Adds AI-ready label
|
||||
|
||||
## Output
|
||||
|
||||
The command produces a complete user story with:
|
||||
- Structured story content
|
||||
- Comprehensive acceptance criteria
|
||||
- DoR validation score
|
||||
- AI-readiness assessment
|
||||
|
||||
## Prerequisites
|
||||
|
||||
**Required:**
|
||||
- None for story generation
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### "Requirements too vague"
|
||||
**Solution:** Add more context about who the user is and what outcome they need
|
||||
|
||||
### "Cannot determine user persona"
|
||||
**Solution:** Specify who will use this feature (e.g., "admin users", "customers", "API consumers")
|
||||
|
||||
### "Scope too large"
|
||||
**Solution:** The command will suggest breaking into multiple stories
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Be Specific:** Include concrete examples of what users need
|
||||
2. **Explain Why:** Mention the business value or problem being solved
|
||||
3. **Note Constraints:** Mention any technical or business limitations
|
||||
4. **Include Context:** Background information helps generate better stories
|
||||
|
||||
---
|
||||
|
||||
**Agent Invoked:** user-story-creation
|
||||
**Skills Used:** story-creator, acceptance-criteria-generator, dor-validator
|
||||
Reference in New Issue
Block a user