gds-dev-story

Execute Dev Story workflows with status tracking, testing, and documentation generation.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-dev-story-joekhosbayar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-dev-story
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/gds-dev-story
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-dev-story-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end story development workflows by consuming a context-rich Dev Story and executing the steps defined in the workflow.

Core Features & Use Cases

  • Guides developers through the Dev Story workflow, loading project context, Dev Notes, and DoD requirements to ensure consistent story delivery.
  • Manages sprint-status interactions, validation gates, and comprehensive documentation updates, including Dev Agent Records and Change Logs.
  • Supports repeatable, auditable story implementation in a multi-step, red-green-refactor lifecycle with clear exit points for halts if blockers arise.

Quick Start

Provide the story file path and allow this skill to execute the story using the context-rich workflow.

Frequently Asked Questions about gds-dev-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end story development workflows for sprint-based tasks?

To automate story development workflows, you provide a context-rich Dev Story file path. The skill executes the defined steps, managing task progression, validation gates, and documentation updates automatically.

What is a context-driven Dev Story and how does it guide implementation?

A context-driven Dev Story is a file containing project context, Dev Notes, and Definition of Done requirements. It guides implementation by providing the workflow steps, architectural guidance, and testing discipline for the automation to execute.

How do I ensure testing discipline and DoD requirements are met during story execution?

To ensure testing discipline and DoD requirements are met, the skill applies validation gates within a red-green-refactor lifecycle. It enforces architectural guidance and tracks task progression against the defined Dev Story workflow.

Can I use this workflow automation for standalone story files outside of a sprint?

Yes, you can use this workflow automation for standalone story files. The skill applies to both sprint-based stories and standalone files, executing steps and handling status tracking identically.

What happens when a blocker arises during automated story task execution?

When a blocker arises during task execution, the workflow provides clear exit points for halting. This ensures the process stops safely, maintaining auditable Dev Agent Records and Change Logs up to that point.