Implement story files into code changes with acceptance evidence.
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill dev-story-wsman
Please help me install this Agent Skill. Skill: dev-story Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/dev-story Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill dev-story-wsman
This Skill removes the friction of turning a written story into a fully implemented, evidence-backed change by gathering the right context, validating dependencies, and guiding the work to completion.
Use the dev-story skill with the path to the active story so it can load context and implement the required changes.
High-intent search queries and answers about installing and using this skill.
To turn story files into shippable code, provide the active story path so the skill can load context, validate ADR and manifest dependencies, route implementation to the correct specialist, and generate review-ready artifacts. It ensures acceptance criteria coverage and test evidence before updating session state.
Validating acceptance criteria during story implementation requires checking each criterion against produced test or smoke evidence and updating the session state. The skill automates this closure by mapping required criteria to generated evidence, ensuring the change is review-ready.
Task routing for different story types works by selecting the right specialist workflow based on the story's layer and technology stack. After loading the story and technical preferences, the skill directs the implementation work to the proper expertise to match the required context.
You need ADR guidance and a control manifest before implementing a story to validate dependency checks and technical context. The skill reads these requirements upfront alongside the TR requirement to ensure the implementation plan aligns with architectural decisions before coding begins.
You can automate evidence tracking for product implementation workflows by routing story files through this skill. It automatically generates required test or smoke evidence, verifies acceptance-criteria coverage, and prepares closure-ready artifacts to update session state for code review.
The session state update upon story implementation closure includes the structured implementation plan, completed code changes, test coverage, and closure-ready evidence. This ensures the next reviewer has all required artifacts and acceptance criteria validation logged for the work session.
emcconnellImplement development story files into source code and automated tests.
cosmicdreamsValidate Drupal patches with PHPCS, PHPStan, and PHPUnit in DDEV.
striderZAScaffold engine-specific test infrastructure and CI workflows for Godot, Unity, or Unreal.
heymishyRead test plans and pipeline-state.json to report per-story and per-AC coverage status.
