Translates a validated story specification into compliant source code and required tests.
npx skills add https://github.com/easonlao/jiazi-game --skill dev-story-easonlao
Please help me install this Agent Skill. Skill: dev-story Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/dev-story Command: npx skills add https://github.com/easonlao/jiazi-game --skill dev-story-easonlao
Dev Story converts a story specification into correct, end-to-end implementation by loading all required planning context, applying architecture rules, routing to the right specialist, and producing the required test coverage so the story can be safely reviewed and closed.
Ask the system to run dev-story on a specific story path to implement the story and create the required source code and test in the project.
High-intent search queries and answers about installing and using this skill.
To generate code from a story spec, the system validates prerequisites like the TR registry, governing ADR, and control manifest, then routes the task to a specialist agent. It writes architecture-compliant source code in src/ and required test coverage in tests/.
Architecture-guided coding enforces ADR compliance by extracting governing ADR decisions and implementation guidelines verbatim. It applies required and forbidden patterns from the control manifest to ensure the generated source code matches architectural rules for the story's layer.
Yes, story implementation supports Godot-ready development by applying engine constraints during the implementation phase. It chooses the proper programmer agent based on the story layer and spawns an engine specialist when engine risk is high.
Yes, a control manifest and governing ADR are required prerequisites. The system validates these dependencies before implementation, blocks when required inputs are missing, and handles manifest version mismatches with explicit user confirmation paths.
When story dependencies are missing, the system blocks implementation to prevent errors. Dependency and version guardrails validate story dependencies upfront and handle manifest version mismatches through explicit user confirmation paths before proceeding.
Agent routing chooses the proper programmer agent based on the story layer, type, and system. It handles Logic, Integration, Visual/Feel, and Config/Data story types, spawning an engine specialist when engine risk is high during the implementation phase.
FrancisVargaGenerates story files from epic GED requirements and ADR decisions with QA-ready acceptance criteria.
nuoyanruoshuiVerify implemented stories against acceptance criteria, design constraints, and test evidence.
nuoyanruoshuiImplement development stories with architectural context and acceptance-criteria validation.
epieczkoValidate and register hook manifest files into the Hook Registry.
