🛠️
AI EngineeringShell

Dev Story

by Donchitos

Dev Story is an AI Engineering skill for Claude Code, published by Donchitos in Claude-Code-Game-Studios.

23.9K stars3.4K forkson Donchitos/Claude-Code-Game-StudiosAdded 2026/08/14Repository updated 2026/05/21
ai-agentsai-assisted-developmentanthropicclaudeclaude-codegame-designgame-developmentgamedevgodotindie-game-devunityunreal-engine
Install in seconds
Install Dev Story
Copy Dev Story into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/dev-story ~/.claude/skills/dev-story

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/Donchitos/Claude-Code-Game-Studios.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.claude/skills/dev-story/SKILL.md in Donchitos/Claude-Code-Game-Studios
Installs to
~/.claude/skills/dev-story
Collection
One of 25 skills cataloged from this repository
Category
AI Engineering2451 skills

What Dev Story does

Dev Story reads a story file, loads full context (story, GDD, ADR, control manifest), routes to the right programmer agent, implements code and test, and confirms each acceptance criterion. Use after /story-readiness and before /code-review.

Dev Story is cataloged under AI Engineering on DirSkills. Dev Story comes from a repository tagged ai-agents, ai-assisted-development, anthropic, claude and claude-code.

Documentation

README

Dev Story

This skill bridges planning and code. It reads a story file in full, assembles all the context a programmer needs, routes to the correct specialist agent, and drives implementation to completion — including writing the test.

The loop for every story:

/qa-plan sprint           ← define test requirements before sprint begins
/story-readiness [path]   ← validate before starting
/dev-story [path]         ← implement it  (this skill)
/code-review [files]      ← review it
/story-done [path]        ← verify and close it

After all sprint stories are done: run /team-qa sprint to execute the full QA cycle and get a sign-off verdict before advancing the project stage.

Output: Source code + test file in the project's src/ and tests/ directories.


This is the opening of the README. Read the full README on GitHub.

Commands Dev Story provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

  • /qa-plan
  • /story-readiness
  • /dev-story
  • /code-review
  • /story-done
  • /team-qa
  • /architecture-review
  • /architecture-decision
  • /create-control-manifest
  • /create-stories

Frequently asked about Dev Story

  • What else does Donchitos publish alongside Dev Story?

    Dev Story is one of 25 skills that DirSkills catalogs from Donchitos/Claude-Code-Game-Studios, the repository it ships in. Its siblings there include Adopt, Architecture Decision and Architecture Review. Each one is a separate skill with its own page in this directory, installs the same way Dev Story does, and is maintained by Donchitos in that same repository. The rest of the collection is listed on the Donchitos/Claude-Code-Game-Studios page.

  • How does Dev Story compare to other AI Engineering skills?

    Dev Story ranks #253 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Dev Story against them. Open each page to compare what they document and how they install.

More from Donchitos/Claude-Code-Game-Studios

Dev Story is one of 25 skills cataloged on DirSkills from Donchitos/Claude-Code-Game-Studios.

See all 25 skills
🔍
2w ago

Adopt

Adopt audits a brownfield project's existing artifacts against the template's required internal formats, classifies gaps by impact, and produces a numbered migration plan. Use it when joining an in-progress project or upgrading from an older template version.
Quality
23.9K3.4K
📐
2w ago

Architecture Decision

Architecture Decision creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Use it when every major technical choice should have a formal, validated ADR in a game development project.
Writing
23.9K3.4K
🏛️
2w ago

Architecture Review

Architecture Review validates that architectural decisions cover all game design requirements, are internally consistent, and target the correct engine version. It builds a traceability matrix, detects cross-ADR conflicts, and produces a PASS/CONCERNS/FAIL verdict.
Quality
23.9K3.4K
🎨
2w ago

Art Bible

Art Bible guides section-by-section authoring of a game's visual identity specification, which gates all asset production. Use it after the game concept is approved and before any game design document authoring.
Writing
23.9K3.4K
🔍
2w ago

Asset Audit

Asset Audit scans game asset directories to check naming conventions, file size budgets, format standards, and pipeline requirements. Use it to identify orphaned assets, missing references, and standard violations before release.
Quality
23.9K3.4K
🎨
2w ago

Asset Spec

Asset Spec generates per-asset visual specifications and AI generation prompts from game design documents, level docs, or character profiles. Use it after the art bible and GDD/level design are approved, before production begins.
AI Engineering
23.9K3.4K