Story Readiness Workflows
Get stories sprint-ready before dev starts.
Three workflows that ensure stories are fully specified, technically refined, and test-planned before a single line of code is written. Each role adds their section to the Jira ticket.
The Problem
Vague stories lead to scope creep, missed edge cases, and rework. When stories enter a sprint without clear acceptance criteria, technical refinement, or test plans, developers fill in the gaps on the fly — and every assumption is a risk.
Vague ACs
“User can log in” — but what about SSO, MFA, session expiry, rate limiting?
Missing technical context
No architecture notes, no API contracts, no affected components. Dev starts from scratch.
No test plan
QE discovers edge cases after implementation. Rework and delayed releases.
Three roles. Three workflows. One sprint-ready story.
Each workflow adds a layer of specification to the Jira ticket, building on what the previous role produced.
Story Draft
Product Owner
PRD-first story creation. Auto-reads linked Confluence PRDs, traces ACs to requirements, flags coverage gaps, and recommends additional stories.
/story-draft DO-2902Story Engineer
Developer
Add technical refinement — reads linked Confluence API specs, scopes analysis with CODEBASE_INSIGHTS, maps components, risks, and sub-tasks.
/story-engineer DO-3238Story QA
QE / SDET
Add test plan across 5 layers. Reads Confluence API specs for contract test assertions and PRD edge cases for test data planning.
/story-qa DO-3238Story Readiness Pipeline
How it works
Generate story workflows
Run the story generator to create workflows tailored to your team's Jira setup and definition of ready.
Draft the story
Product owner runs /story-draft with a concept or existing ticket. The workflow auto-reads linked Confluence PRDs, creates PRD-traced ACs, scope boundaries, coverage analysis, and recommends additional stories for uncovered requirements.
Engineer the story
Developer runs /story-engineer on the drafted ticket. Adds architecture notes, affected components, API contracts, risks, and implementation sub-tasks.
QA the story
QE runs /story-qa on the engineered ticket. Adds test plan across 5 layers, test data requirements, edge case datasets, and coverage targets.
Hand off to development
The story is sprint-ready. Run /feature-build with the ticket ID and the development workflow has full context from day one.
Workflow Comparison
| Aspect | Story Draft | Story Engineer | Story QA |
|---|---|---|---|
| Role | Product Owner | Developer | QE / SDET |
| Input | Concept, epic/story, or Confluence PRD | Drafted story + Confluence API specs | Engineered story + Confluence specs |
| Output | PRD-traced ACs, scope, edge cases, coverage matrix | Architecture, components, API contracts, sub-tasks | Test plan (5 layers), test data, coverage targets |
| Phases | ~6 phases | ~5 phases | ~6 phases |
| Signal | STORY_DRAFTED | STORY_ENGINEERED | STORY_SPRINT_READY |