dev-story

Implement game development story specifications into code and tests.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill dev-story-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/dev-story
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill dev-story-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev Story eliminates the gap between high-level story/spec documents and working, test-covered implementation by coordinating context loading, agent routing, and code/test completion in a single guided flow.

Core Features & Use Cases

  • Story-to-implementation pipeline: Reads a story file (or the active story) and drives implementation through completion, including required tests.
  • Context and governance validation: Loads TR registry, governing ADR, control manifest, and engine preferences, enforcing required files and warning on non-critical ones.
  • Acceptance-criterion-driven coding: Ensures Logic/Integration criteria are covered with automated tests and summarizes coverage and deviations.
  • Engine-appropriate specialist routing: Chooses the correct programmer agent by story layer/type, and conditionally spawns engine specialists based on ADR risk and engine compatibility needs.

Quick Start

Use the dev-story skill to implement the currently active story by saying: "Run /dev-story with no arguments to continue the active story implementation."

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I turn a game development story specification into working code?

Story-to-implementation pipelines convert story specifications into working code by loading documentation, enforcing architecture governance via ADRs, routing to engine specialists, and producing source changes with required test evidence.

How does agent orchestration handle story implementation for different game engine layers?

Agent orchestration routes story implementation by selecting the correct programmer agent based on story layer type, such as Logic, Visual, or Config, and conditionally spawns engine specialists based on ADR risk and compatibility needs.

How do I automate test creation from acceptance criteria in a story spec?

Automated test creation from acceptance criteria ensures Logic and Integration requirements are covered by generating tests in specified paths, then summarizes test coverage and any deviations from the governing specification.

What is architecture governance in code generation and when is it needed?

Architecture governance in code generation enforces control-manifest rules, validates manifest-version alignment, and loads TR registries, ensuring reliable implementation when applying changes across complex game engine configurations.

Can I use story spec implementation with existing control manifests and ADRs?

Story spec implementation works with existing control manifests and ADRs by loading the TR registry, validating manifest-version alignment, and enforcing required files while warning on non-critical missing dependencies.

Why does story implementation fail when dependency validation is missing?

Story implementation fails without dependency validation because the pipeline enforces control-manifest rules and ADR governance, requiring specific files to be present before routing engine specialists and generating code.