gds-dev-story

Implements game development stories from sprint specs using red-green-refactor cycles.

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-dev-story-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-dev-story
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/gds-dev-story
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-dev-story-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates the disciplined execution of game development stories by turning a context-filled story spec into working, tested code while keeping sprint status and story files synchronized. ## Core Features & Use Cases - Sprint-Aware Story Discovery: Automatically finds the next ready-for-dev story from sprint-status.yaml or accepts an explicit story file path. - Test-Driven Implementation: Executes each task with a red-green-refactor cycle, writes unit, integration, and end-to-end tests, and runs full regression suites before marking tasks complete. - Review Continuation: Detects prior senior developer code reviews, prioritizes unresolved review follow-up items, and tracks their resolution. - Use Case: A game developer says "implement the next story in the sprint plan" and the workflow loads the story, implements every task with tests, updates the story file and sprint status to review, and reports a completion summary. ## Quick Start Ask the agent to implement the next story in the sprint plan or say "dev this story" followed by the path to your story 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?▼

Run the dev-story workflow and it reads sprint-status.yaml to find the first story marked ready-for-dev, loads its full context, and implements every task with tests until all acceptance criteria are satisfied.

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

Each task follows a red-green-refactor cycle: failing tests are written first, minimal code makes them pass, then the code is refactored while keeping tests green. Regression and new tests must pass before any task is marked complete.

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 resolving those findings before continuing with remaining regular tasks.

What happens if no ready-for-dev story exists in the sprint?▼

The workflow reports that no ready stories were found and offers options: run create-story to draft the next story, run validate-create-story for a quality check, or provide a specific story file path to develop.

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

It halts when the story file is inaccessible, requirements are ambiguous, new dependencies beyond the spec are needed, configuration is missing, three consecutive implementation failures occur, or validation gates fail.