skills.rest
nevesb
nevesbCOMMUNITY
Explore all skills by this author →
GitHub

dev-story

Loads TR registry, ADR, manifest, engine prefs to implement Logic and Integration game stories with automated tests.

Updated Aug 27, 2026
Search Tags:#automation#adr#story#test#implement#engine#gdd
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill dev-story-nevesb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill dev-story-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between planning and implementation by reading a story file, assembling all design and architectural context, routing work to the correct programmer and engine specialists, and driving a complete implementation that includes automated tests where required.

Core Features & Use Cases

  • Context assembly: Loads story content, the TR registry requirement, governing ADR, control manifest rules, engine preferences, and session state before any implementation begins.
  • Validation and routing: Validates dependencies and manifest versions, decides which programmer and engine specialist to spawn, and enforces ADR and manifest guardrails.
  • Implementation orchestration: Orchestrates agent-driven file creation and test authoring, collects implementation artifacts, handles blockers and deviations, and updates session state for traceability.
  • Use Case: Use when a Ready story in production/epics must be implemented end-to-end into src/ with an accompanying test under tests/, following ADR guidance and control manifest rules.

Quick Start

Run /dev-story with the path to a Ready story file to load context, spawn the appropriate programmer and engine specialists, implement the code, and write the required test.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I implement game development stories into production code with automated tests?▼

To implement game development stories into production code, this Skill reads story files, loads governing ADRs and control manifests, routes work to programmer and engine specialists, and generates working source code with automated tests.

What is the best way to enforce ADR guardrails and manifest rules during story implementation?▼

Enforcing ADR guardrails and manifest rules during story implementation is achieved by validating dependencies and manifest versions before spawning agents, ensuring all architectural constraints are applied throughout the file creation and test authoring process.

Do I need a TR registry and engine preferences to automate story file implementation?▼

Yes, you need a TR registry and engine preferences to automate story file implementation. The Skill requires full context, including the TR registry requirement, governing ADR, control manifest, and engine preferences, before any coding begins.

How does routing to programmer and engine specialists work for Logic and Integration stories?▼

Routing to programmer and engine specialists works by validating the story file and session state, then deciding which specialist to spawn to orchestrate agent-driven file creation and test authoring for Logic and Integration stories.

Can I use this to trace implementation artifacts back to GDD TR-IDs in production epics?▼

Yes, you can use this to trace implementation artifacts back to GDD TR-IDs in production epics. It collects implementation artifacts, handles blockers and deviations, and updates session-state metadata for full traceability.

What happens if a story file has missing dependencies or invalid manifest versions?▼

If a story file has missing dependencies or invalid manifest versions, the validation phase will identify the blockers before implementation begins. The Skill handles deviations and updates session state to record why the process could not proceed.

Related Skills

Explore More Software Engineering Skills→
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
mattgierhartmattgierhart
193

ghm-status-sync

Synchronize README Command Center dashboard sections with current project state.

Community
Intermediate
emcconnellemcconnell

dev-story

Implement development story files into source code and automated tests.

Community
Advanced
FrancisVargaFrancisVarga

dev-story

Implement game development stories into scoped source code and tests.

Community
Advanced