SSDET Workflow Framework

Getting Started

Story Readiness

Set up story readiness workflows and get stories sprint-ready before development begins.

What Is This?

The story readiness pipeline ensures stories are fully specified before development starts. Three workflows — one per role — each add a layer of specification to the Jira ticket until it's sprint-ready.

After setup, you'll have three slash commands: /story-draft (Product Owner), /story-engineer (Developer), /story-qa (QE/SDET). Once a story is sprint-ready, hand it off to /feature-build for development.

Prerequisites

  • Claude Code CLI installed and authenticated
  • A repository with the framework copied in
  • Jira MCP integration — required for story readiness workflows (they read and write to Jira tickets)

Setup

1

Copy the framework into your repo

Copy the .claude folder into the root of your repository. This folder contains:

  • commands/generate-story-workflows.md — story readiness generator
  • story-generator/ — story readiness phases and templates
bash
# From the framework source
cp -r .claude /path/to/your-repo/.claude
2

Open Claude Code in your repo

Navigate to your repository root and launch Claude Code. It will automatically detect the .claude/commands/ directory and make the generators available as slash commands.

bash
cd /path/to/your-repo
claude
3

Generate story readiness workflows

The story generator creates workflows for getting stories sprint-ready before development begins. It has its own survey phase that analyzes your team's Jira setup, definition of ready, and project conventions.

bash
/generate-story-workflows

This creates three workflow commands — one per role:

  • /story-draft — Product Owner: PRD-first story creation with requirement traceability and coverage analysis
  • /story-engineer — Developer: add architecture, components, API contracts, sub-tasks
  • /story-qa — QE/SDET: add test plan (5 layers), test data, coverage targets
4

Start using story workflows

Run the workflows in sequence — each role adds their section to the Jira ticket:

bash
# 1. Product owner drafts the story (auto-reads linked Confluence PRDs)
/story-draft DO-3255

# Or provide a PRD URL explicitly
/story-draft DO-3255 --prd https://your-site.atlassian.net/wiki/spaces/XX/pages/12345/PRD+Title

# Or create from scratch
/story-draft "Build a recommendation engine"

# 2. Developer adds technical refinement
/story-engineer DO-3238

# 3. QE adds test plan
/story-qa DO-3238

# 4. Story is sprint-ready — hand off to development
/feature-build DO-3238

Next steps

Explore the individual workflow pages: Story Draft, Story Engineer, Story QA. Or set up the Development Workflows to execute sprint-ready stories.