dev-story

Implements sprint stories from spec files using a red-green-refactor workflow with status tracking.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/stellar-zk/stellar-zk --skill dev-story-stellar-zk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/stellar-zk/stellar-zk/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/stellar-zk/stellar-zk --skill dev-story-stellar-zk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the ambiguity and inconsistency of turning a written story spec into working code by enforcing a strict, step-by-step implementation workflow with test-driven development, validation gates, and automatic sprint status updates. ## Core Features & Use Cases - Story Discovery & Execution: Automatically finds the next ready-for-dev story from sprint-status.yaml or accepts an explicit story file path, then implements every task and subtask in order. - Red-Green-Refactor TDD Cycle: Writes failing tests first, implements minimal code to pass, then refactors while keeping tests green, with HALT conditions for failures or missing configuration. - Review Continuation & Definition of Done: Detects prior code review findings, resolves follow-up items, and validates a comprehensive definition-of-done checklist before marking the story ready for review. - Use Case: A developer says "implement the next story in the sprint plan" and the workflow locates story 1-2-user-authentication, marks it in-progress, implements all tasks with tests, updates the File List and Change Log, and sets the status to review. ## Quick Start Tell the assistant to dev this story by providing the path to your story spec file, or ask it to implement the next ready story in the sprint plan.

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?▼

Run 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 the dev story workflow handle test-driven development?▼

It enforces a red-green-refactor cycle for each task: write failing tests first, implement minimal code to make them pass, then refactor while keeping tests 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, extracts pending action items by severity, and prioritizes those review follow-up tasks before continuing regular tasks, marking both the task and the review item resolved.

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

The workflow halts and offers options: run create-story to draft the next story, run validate-create-story for a quality check, provide a specific story file path, or review the current sprint status in detail.

What are the limitations of the dev story workflow?▼

It only modifies permitted story file sections and never implements anything not mapped to a task or subtask. It halts on missing configuration, ambiguous requirements, unapproved new dependencies, or three consecutive implementation failures.