dev-story

Implements sprint stories from spec files using red-green-refactor cycles and definition-of-done validation.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/JHAMILCALI/Stellar-Build --skill dev-story-jhamilcali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/JHAMILCALI/Stellar-Build/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/JHAMILCALI/Stellar-Build --skill dev-story-jhamilcali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written story spec into working, tested code requires disciplined execution: finding the next ready story, following tasks in order, writing tests, and updating sprint tracking. This Skill automates that entire developer workflow so stories are implemented completely and consistently without skipped steps. ## Core Features & Use Cases - Sprint-Aware Story Discovery: Automatically finds the next story marked "ready-for-dev" in sprint-status.yaml or accepts an explicit story file path. - Test-Driven Implementation: Executes each task using a red-green-refactor cycle, writing failing tests first and validating against all acceptance criteria. - Review Continuation: Detects prior code review findings, prioritizes unresolved review follow-up tasks, and marks them resolved in both the task list and review section. - Use Case: A developer says "implement the next story in the sprint plan" and the Skill locates the story, implements every task with tests, updates the story file and sprint status to "review", and reports a completion summary. ## Quick Start Tell the AI to dev this story by providing the story file path, 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?▼

Ask the AI to implement the next story in the sprint plan. The Skill reads sprint-status.yaml, finds the first story marked ready-for-dev, loads its full context, and executes all tasks with tests until the story reaches review status.

How does the dev-story workflow handle test-driven development?▼

It follows a red-green-refactor cycle per task: write failing tests first, implement minimal code to pass them, then refactor while keeping tests green. It never marks a task complete until all tests exist and pass with no regressions.

Can I specify a particular story file instead of auto-discovery?▼

Yes, provide the full story file path with a command like "dev this story [story file]". The Skill uses that path directly, skipping sprint-status discovery, and extracts the story key from the filename or metadata.

What happens when a story has unresolved code review findings?▼

The Skill detects the Senior Developer Review section, counts unchecked action items by severity, and prioritizes review follow-up tasks marked [AI-Review] before regular tasks. Resolved items are checked off in both the task list and the review section.

Which parts of the story file can the workflow modify?▼

Only five areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log and Completion Notes), File List, Change Log, and Status. All other story content remains untouched to preserve the original specification.

When does the dev-story workflow halt instead of completing?▼

It halts when the story file is inaccessible, task requirements are ambiguous, new dependencies beyond the spec are needed, three consecutive implementation failures occur, required configuration is missing, or definition-of-done validation fails.