Overview

Story Development uses test-driven development to implement user stories. It derives tests from acceptance criteria, writes failing tests, implements minimal code to pass, and refactors while keeping tests green. It outputs a passing implementation, a list of changed files, acceptance criteria verification, and implementation notes.

How This Skill Works

Begin by reading the complete story and acceptance criteria. For each criterion, write a failing test, then implement the minimum code required for the test to pass. Refactor while keeping tests green, run the full test suite, and document implementation decisions and file changes.

When to Use It

• When kicking off a new user story in a sprint with clear acceptance criteria
• When the implementation requirements are defined but code structure is unclear
• When you want to ensure features meet testable specs through TDD
• When you need traceable outputs: list of changed files, tests, and notes
• When documenting design decisions after implementation

Quick Start

1. Step 1: Read story and acceptance criteria
2. Step 2: Write failing tests for each criterion
3. Step 3: Implement minimum code to pass tests and run full suite

Best Practices

• Capture acceptance criteria as testable specifications before coding
• Write failing tests for every criterion to guide implementation
• Implement the minimal code needed to pass all tests
• Refactor with tests green and update tests if behavior changes
• Document decisions, file changes, and rationale in notes

Example Use Cases

• Add a login feature with authentication criteria and tests
• Implement a data transformation story with tests for edge cases
• Create an API endpoint test and verify via automated tests
• Refactor a feature after TDD while preserving behavior
• Record implementation notes and changed files in PR documentation

Frequently Asked Questions