---
name: bmAD-technical-story-refiner
description: >-
  Guide for transforming user stories into actionable, technically detailed specifications
  ready for implementation. This skill should be used when stories need detailed technical
  design before development begins.
---

# Technical Story Refiner Skill

This skill guides the detailed technical refinement of individual stories following the BMAD methodology.

## When to Use This Skill

- User has a backlog of approved stories
- Stories need detailed technical design
- Implementation steps need to be defined
- Technical dependencies need to be clarified

## When NOT to Use This Skill

- User needs to create the initial story backlog (use Product Owner mode)
- User wants to implement stories directly (use Story Developer mode)
- User only has high-level requirements without stories
- User needs architecture design (use Software Architect mode)

## Workflow

### Step 1: Read Source Documents

Use `read_file` tool to extract content from:
- `project_requirements.md` - Functional specifications
- `project_architecture.md` - Technical architecture
- `project_stories.md` - Story backlog

### Step 2: Select Story for Refinement

Identify the next story to refine based on:
- Priority
- Dependencies
- Sprint assignment

### Step 3: Define User Story Format

Ensure story follows standard format:
```
As a [role]
I want [action]
so that [benefit]
```

### Step 4: Provide Context and Background

Document:
- Business context and drivers
- Current pain points or limitations
- Expected improvements
- Impact on users or business

### Step 5: Define Technical Design

For each story, specify:
- **Data Model** - Objects, fields, relationships
- **API Design** - Endpoints, contracts
- **Business Logic** - Rules and validations
- **UI/UX** - Interface requirements
- **Error Handling** - Edge cases

### Step 6: Set Estimation and Criteria

Define:
- Story points
- Sprint assignment
- Priority
- Dependencies (prerequisites, blocking, blocked by)
- Module/Component
- Complexity (Low/Medium/High)
- Acceptance criteria (numbered, testable)

### Step 7: Generate Story Document

Create individual `story_N.md` files using the template in `assets/story-N-template.md`.

## Output

The deliverables are `story_N.md` files - detailed technical specifications for each story.

## Templates

- `assets/story-N-template.md` - Document template for detailed story

## References

- BMAD workflow: Phase 5 of 8-stage Agile development