dev-story

Execute story implementations from spec files with red-green-refactor cycles.

9|66|Updated Oct 13, 2025

Search Tags:#automation #sprint #develop #tests #story-workflow #dev-notes

Ready to run

npx skills add https://github.com/salazarsebas/Cougr --skill dev-story-salazarsebas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/salazarsebas/Cougr/tree/main/.codex/skills/dev-story
Command: npx skills add https://github.com/salazarsebas/Cougr --skill dev-story-salazarsebas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between story planning and actual code by driving the automated implementation of stories from a context-rich spec file.

Core Features & Use Cases

Context-driven development: loads Dev Notes and project context to guide implementation.
Red-Green-Refactor discipline: enforces test-first development and iterative refinement.
Sprint-aware progress: updates sprint-status and Dev Agent records as work proceeds, ensuring traceability.

Quick Start

Provide the story file path and run the dev-story workflow to begin implementing the first incomplete task.

Frequently Asked Questions about dev-story

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

FAQPage Schema

How do I automate story implementation from a spec file?▼

Automating story implementation requires loading a context-rich spec file with Dev Notes and acceptance criteria to drive an end-to-end development workflow. The process executes story tasks sequentially, ensuring traceability by updating sprint status and Dev Agent records as work proceeds.

What is the red-green-refactor cycle in test-first development?▼

The red-green-refactor cycle enforces test-first development by writing failing tests first, implementing code to pass them, and iteratively refining the result. This discipline ensures iterative refinement and validates the Definition of Done across tests during story implementation.

How do I maintain sprint traceability when automating feature development?▼

Sprint traceability is maintained by automatically updating sprint-status and Dev Agent records as development proceeds. The workflow ensures all implemented features are logged in Change Logs and validated against the Definition of Done across tests.

Do I need acceptance criteria and Dev Notes to automate a development workflow?▼

Yes, acceptance criteria and Dev Notes are required inputs to drive context-driven development. The spec file provides the necessary project context to guide implementation, enforce the red-green-refactor cycle, and validate the Definition of Done.

Can I use story specs for sprint-based process automation?▼

Yes, story specs are designed for teams following a sprint-based process. The workflow applies to stories defined with Dev Notes and acceptance criteria, enforcing test-first development and updating sprint status automatically.

What's the best way to bridge story planning and actual code implementation?▼

Bridging story planning and code requires an automated workflow that reads a context-rich spec file and executes story implementations. It enforces a strict red-green-refactor cycle and updates sprint status, Dev Agent Records, and Change Logs to ensure traceability.