gds-dev-story

Implements sprint stories end-to-end following story spec files with red-green-refactor cycles.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-dev-story-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-dev-story
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-dev-story
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-dev-story-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the disciplined execution of a development story: finding the next ready story in the sprint plan, implementing every task with tests, and updating tracking files, without losing rigor or skipping steps. ## Core Features & Use Cases - Sprint-Aware Story Discovery: Reads sprint-status.yaml to find the first story marked ready-for-dev, or accepts an explicit story file path. - Red-Green-Refactor Implementation: Writes failing tests first, implements minimal code to pass, then refactors while keeping tests green, task by task. - Review Continuation Handling: Detects prior senior developer review sections and prioritizes unresolved review follow-up items before regular tasks. - Definition-of-Done Gating: Validates all acceptance criteria, tests, file lists, and changelogs before marking the story as review. - Use Case: A developer on the MingGoRTS project says "dev this story" and the workflow implements the next sprint story, runs the full CTest suite, and updates sprint-status.yaml to review. ## Quick Start Tell the assistant to dev the next story in the sprint plan or provide a specific story file path to implement.

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 my sprint plan?

Invoke the workflow with a phrase like "implement the next story in the sprint plan". It reads sprint-status.yaml, finds the first story marked ready-for-dev, and executes all its tasks in order until completion.

How does the dev story workflow handle code review follow-ups?

It detects a Senior Developer Review section in the story file, counts unchecked action items by severity, and prioritizes those review follow-up tasks before continuing with regular tasks, marking both the task and the review item resolved.

What happens if no story is marked ready-for-dev?

The workflow halts and offers options: run create-story to draft a new story, run validate-create-story to improve existing stories, provide a specific story file path, or review the current sprint status in detail.

Which 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 sections. All other story content is treated as a frozen specification.

When does the dev story workflow stop before completion?

It halts only on explicit conditions: ambiguous task requirements, new dependencies needing approval, three consecutive implementation failures, missing configuration, failing regression tests, or failed definition-of-done validation.