skills.rest
emcconnell
emcconnellCOMMUNITY
Explore all skills by this author →
GitHub

dev-story

Implement development story files into source code and automated tests.

Updated Apr 10, 2026
Search Tags:#adr#orchestration#test-generation#agent-routing#dependency-validation#story-implementation
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill dev-story-emcconnell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/emcconnell/nova-scout --skill dev-story-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the handoff from planning to implementation by reading a story file, assembling all governing context (GDD/TR, ADR, control manifest, engine prefs), validating dependencies and manifest versions, and orchestrating specialist programmer agents to produce code and tests. It reduces coordination overhead, prevents design drift, and enforces ADR and control-manifest constraints so engineers can implement stories reliably.

Core Features & Use Cases

  • Context aggregation: Loads the story, TR registry requirement, governing ADR decision and guidelines, control manifest rules, and engine preferences before any code is written.
  • Dependency & manifest validation: Verifies dependency story statuses and manifest version alignment and prompts the user when risks are detected.
  • Agent routing & orchestration: Chooses primary programmer and engine specialist agents based on story layer, type, and engine, then spawns tasks to implement code and tests.
  • Test-first enforcement: Ensures Logic and Integration stories include automated tests and places Visual/Feel evidence notes for manual verification.
  • Error recovery & session updates: Surfaces blockers immediately, offers remediation choices, and appends session extracts to session-state for traceability.

Quick Start

Run the dev-story skill on the path to your target story file to validate context and implement the story into source and test files.

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 sprint files into source code and tests?▼

Automating story implementation involves reading a story file, validating dependencies and ADR context, then routing specialist agents to generate production-ready source code and automated tests. This skill orchestrates that entire workflow, reducing manual coordination and preventing design drift.

What is ADR-based dependency validation for sprint story workflows?▼

ADR-based dependency validation checks governing architecture decision records, control manifests, and prior story statuses before implementation begins. It ensures manifest versions align and surfaces dependency risks immediately, prompting you for remediation choices to prevent design drift.

Do I need a TR registry and control manifest to implement stories with agent routing?▼

Yes, a TR registry and control manifest are required. This skill operates on engine-driven projects that use these artifacts to load design context, verify TR and ADR presence, check manifest versions, and route engine specialist agents appropriately during story implementation.

Can I enforce test-first development when automating story file implementation?▼

Yes, test-first enforcement is built into the workflow. Logic and Integration stories automatically include generated automated tests, while Visual and Feel stories place evidence notes for manual verification, ensuring test coverage aligns with story type.

What's the best way to handle blockers and session traceability during story implementation?▼

Handling blockers requires surfacing errors immediately and offering remediation choices. This skill appends session extracts to session-state for traceability, ensuring that every blocker and resolution during agent orchestration is documented for downstream review.

Why does story implementation fail when ADR or control manifest versions are misaligned?▼

Story implementation fails because dependency and manifest validation checks for ADR presence and version alignment before spawning programmer agents. Misaligned manifests or missing ADRs trigger immediate blocker detection, prompting you to resolve the context gap before code generation proceeds.

Related Skills

Explore More Software Engineering Skills→
adolfoaranaes12adolfoaranaes12
2

validate-story

Validate Markdown stories for template compliance and implementation readiness.

Community
Advanced
garochee33garochee33
3

check

Verify recent work by reviewing session traces, inspecting state, and running build and test checks.

Community
Advanced
striderZAstriderZA
72

architecture-decision

Create Architecture Decision Records with context, alternatives, and consequences.

Community
Advanced
easonlaoeasonlao

dev-story

Translates a validated story specification into compliant source code and required tests.

Community
Advanced