dev-story

Implement sprint stories into production code with required automated tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev-story removes the friction between story planning and working code by turning a fully specified sprint story into an implementation plus the required automated test, with guardrails that keep you aligned to the controlling ADR, TR requirements, and layer rules.

Core Features & Use Cases

  • Full context assembly for programmers: Reads the story, TR registry requirement text, governing ADR implementation guidelines, and control manifest rules for the story’s layer, so implementation follows the source of truth rather than stale narrative.
  • Dependency and readiness validation: Validates that story dependencies exist and are in an acceptable status before implementation, and blocks progress when TR/ADR essentials are missing.
  • Automated test creation and coverage: Enforces creation of the test file required by Logic/Integration stories and maps acceptance criteria to test functions.
  • Session-state and sprint bookkeeping: Marks sprint status as in-progress and updates the story’s Last Updated field to support staleness detection.
  • Use Case: When a hatchery sprint story is marked ready, run dev-story to implement the feature and its tests, then proceed to code review and story closure.

Quick Start

Use dev-story with a story path like 'production/epics/hatchery/story-005-dragon-unlock-duplicate-xp-and-shiny-upgrade.md' to implement that story with the correct context and required tests.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I implement a sprint story end-to-end with required automated tests?

To implement a sprint story end-to-end with tests, use dev-story to read story files, TR registry requirements, and ADR guidelines, then delegate code and test creation to specialist programmers while mapping acceptance criteria to test functions.

What is the best way to ensure story implementation follows ADR compliance and layer rules?

Ensuring story implementation follows ADR compliance requires reading the control manifest and governing ADR implementation guidelines before coding. The dev-story skill validates these architecture documents and blocks progress if TR or ADR essentials are missing.

How does story dependency validation work before starting implementation?

Story dependency validation checks that required dependencies exist and hold an acceptable status before implementation begins. This readiness validation prevents starting work on stories with unresolved prerequisites or missing governing architecture documents.

Can I use automated test creation for Config and Data sprint stories?

Automated test creation via dev-story applies only to Logic and Integration story workflows. It skips agent spawning and test enforcement for Config and Data stories, focusing specifically on engine routing and dependency validation for logic-based tasks.

How do I handle sprint workflow bookkeeping and staleness detection during implementation?

Handling sprint workflow bookkeeping involves marking sprint status as in-progress and updating the story's Last Updated field automatically during implementation. This session-state tracking supports staleness detection for active development cycles.

Does dev-story work with Godot engine story routing and TR registry requirements?

Dev-story works with Godot engine routing decisions by validating TR registry requirements and applying layer rules from the control manifest. It processes engine and routing parameters specifically for Logic and Integration story workflows.