gds-dev-story

Implements sprint stories from spec files using red-green-refactor test-driven development.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-dev-story-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-dev-story
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-dev-story
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-dev-story-hordricjr

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, loading project context, writing tests first, and tracking status. This Skill automates that entire developer workflow so a story goes from ready-for-dev to review in one continuous run. ## Core Features & Use Cases - Sprint 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/subtask with a red-green-refactor cycle, writing failing tests before minimal implementation. - Status & Review Tracking: Updates story checkboxes, File List, Dev Agent Record, Change Log, and sprint status, including resuming work after a code review. - Use Case: A developer says "implement the next story in the sprint plan" and the Skill loads the story spec, implements every task with tests, runs the full regression suite, and marks the story ready for review. ## Quick Start Implement the next ready-for-dev story from the sprint plan following its spec file.

Frequently Asked Questions about gds-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 spec, and implements every task with tests. You can also pass an explicit story file path to develop a specific story.

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

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 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, and prioritizes those [AI-Review] tasks before continuing regular tasks, marking both the task and the review action item resolved.

What parts of the story file can the workflow modify?

Only the YAML frontmatter baseline_commit, Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status. All other story content is treated as a frozen spec that cannot be altered during implementation.

What happens when no ready-for-dev stories exist in the sprint?

The workflow halts and offers options: run create-story to draft the next story from epics, run validate-create-story for a quality check, specify a story file path manually, or review the current sprint status.