skills.rest
WindXRan
WindXRanCOMMUNITY
Explore all skills by this author →
GitHub

dev-story

Convert story files into implementation and test evidence using ADR and control-manifest rules.

Updated Apr 4, 2026
Search Tags:#agent routing#ADR compliance#session state#test evidence#story implementation#dependency validation#architecture rules
One-click install
npx skills add https://github.com/WindXRan/y3td --skill dev-story-windxran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/WindXRan/y3td --skill dev-story-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev Story turns a high-level story specification into working source code and a required test, while ensuring the implementation follows the governing ADR, architecture requirements, control manifest rules, and current engine preferences.

Core Features & Use Cases

  • Story-to-implementation orchestration: Reads a story file (or the currently active story), loads TR/GDD, governing ADR, and control-manifest rules, then routes to the correct specialist agent for the story’s layer/type/system.
  • Acceptance-criteria-driven delivery: Forces Logic/Integration stories to create the specified test evidence file and cover every acceptance criterion before completion.
  • Guardrails and dependency safety: Blocks implementation when critical architecture context is missing (TR registry or governing ADR), validates story dependencies’ status, and handles manifest-version staleness via user confirmation.

Quick Start

Run dev-story to implement the currently active story from your session state.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I implement user stories while ensuring test evidence and ADR compliance?▼

Story implementation enforces ADR compliance and test evidence by loading governing requirement rules, routing to specialist agents by layer type, and blocking completion until all acceptance criteria are covered by tests.

What happens if my story is missing critical architecture context like the governing ADR?▼

Missing critical architecture context blocks story implementation entirely. The workflow validates dependency status and requires the TR registry and governing ADR to be present, halting execution to ensure architectural safety.

How do I handle manifest-version staleness when routing agent tasks for story implementation?▼

Manifest-version staleness is handled via explicit user confirmation. The workflow detects outdated control-manifest versions during agent routing and prompts the user before proceeding with implementation.

Can I implement different types of stories such as Logic, Integration, and Visual using automated routing?▼

Automated routing supports Logic, Integration, Visual/Feel, and Config/Data story types. It directs each story to the appropriate specialist agent based on layer, type, and system rules defined in the control manifest.

How do I start implementing the currently active story from my session state?▼

Implementing the active story from session state requires running the dev-story workflow. It automatically reads the active story file, loads the matching TR requirement and ADR guidelines, then orchestrates the implementation end-to-end.

Related Skills

Explore More Software Engineering Skills→
epieczkoepieczko

hook.register

Validate and register hook manifest files into the Hook Registry.

Community
Intermediate
wsmanwsman
18

dev-story

Implement story files into code changes with acceptance evidence.

Community
Advanced
imgamerimgamer

dev-story

Transform story specs into source code and tests with architecture validation.

Community
Advanced
wsmanwsman
18

story-readiness

Validate implementation-ready stories and flag missing requirements before development begins.

Community
Advanced