dev-story

Implements sprint stories from spec files using test-driven development and status tracking.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/chrissstellee/Movix --skill dev-story-chrissstellee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/chrissstellee/Movix/tree/main/.agents/skills/dev-story
Command: npx skills add https://github.com/chrissstellee/Movix --skill dev-story-chrissstellee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork from turning a written story spec into working code by enforcing a strict, ordered implementation workflow with test-first development, validation gates, and automatic sprint status updates. ## Core Features & Use Cases - Story Discovery & Loading: Automatically finds the next ready-for-dev story from sprint-status.yaml or accepts an explicit story file path. - Red-Green-Refactor Execution: Implements each task with failing tests first, minimal passing code, then refactoring, with HALT conditions for blockers. - Review Continuation: Detects prior code review findings and prioritizes unresolved review follow-up tasks before regular work. - Definition-of-Done Validation: Verifies all tasks, tests, file lists, and acceptance criteria before marking a story ready for review. - Use Case: A developer says "implement the next story in the sprint plan" and the workflow locates the story, implements every task with tests, updates sprint-status.yaml, and hands off a review-ready result. ## Quick Start Ask the assistant to implement the next story in the sprint plan, or provide a specific story file path to develop.

Frequently Asked Questions about dev-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement the next story in a sprint plan automatically?▼

Invoke the dev-story workflow and it reads sprint-status.yaml to find the first story marked ready-for-dev, loads its full spec, and implements every task in order. You can also pass an explicit story file path to develop a specific story.

How does test-driven development work in a story implementation workflow?▼

Each task follows a red-green-refactor cycle: failing tests are written first, then minimal code makes them pass, then the code is refactored while tests stay green. A task is only marked complete when all its tests exist and pass with no regressions.

Can the workflow resume a story after a code review?▼

Yes. It detects a Senior Developer Review section in the story file, counts unchecked review follow-up items by severity, and prioritizes resolving those findings before continuing with regular tasks.

What happens if no ready-for-dev stories are found?▼

The workflow reports the current sprint status and offers options: run create-story to draft a new story, run validate-create-story to improve existing ones, or provide a specific story file path to develop.

When does the workflow stop or halt during implementation?▼

It halts when new dependencies beyond the story spec are needed, after three consecutive implementation failures, when required configuration is missing, or when validation gates fail. Otherwise it runs continuously until all tasks are complete.