skills.rest
EvanPluchart
EvanPluchartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-story

Orchestrate tracked software story implementation with a 10-step workflow and git checkpoints.

2|Updated Mar 19, 2026
Search Tags:#workflow automation#story implementation#git checkpoint#sprint tracking#parallel workers#adaptive context loading#tests and documentation
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill dev-story-evanpluchart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill dev-story-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how implementation “stories” are executed so each change is tracked, validated, tested, documented, committed, and marked complete with minimal drift from project conventions.

Core Features & Use Cases

  • 10-step end-to-end story execution: pre-flight validation, adaptive context loading, git checkpointing, implementation, cascade impact checks, targeted tests, documentation updates, lessons learned, standardized commit, and final status/proposal of next story.
  • Flexible execution modes: supports single story by ID, auto-selecting the next available story, sequential batch runs, parallel worker execution with file-conflict avoidance, and epic-scoped execution (sequential or as parallel as possible).
  • Adaptive context loading for safer, faster assistance: loads only evan-workflow docs relevant to the story’s stack/scopes and patterns, explicitly avoiding full technos directory ingestion.

Quick Start

Run the story implementation for a specific story by providing its ID with the command: “Use dev-story with --story <id> and follow the 10-step workflow to implement, test, document, and mark it done in sprint-status.yaml.”

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I enforce a strict workflow for sprint story implementation with git checkpointing?▼

Story implementation is enforced through a strict 10-step workflow that includes pre-flight validation, git safety checkpoints, targeted tests, and documentation updates before marking the story done in sprint-status.yaml.

Can I run story execution in parallel workers without causing file conflicts?▼

Yes, parallel worker execution is supported with built-in file-conflict avoidance. The workflow also supports single story, sequential batch runs, and epic-scoped execution modes for flexible sprint tracking.

How does adaptive context loading work for workflow automation during story implementation?▼

Adaptive context loading works by ingesting only the relevant manifests and patterns for a story's specific stack and scopes. This explicitly avoids loading the full technos directory to ensure safer and faster assistance.

Do I need to update tests and documentation before marking a tracked story as done?▼

Yes, updating tests and documentation is mandated before final status transitions. The workflow requires targeted tests, documentation updates, and a standardized commit to ensure each change is fully validated and tracked.

What is the best way to execute an entire epic scope sequentially or as parallel as possible?▼

Epic-scoped execution allows you to process a group of stories either sequentially or as parallel as possible. The workflow manages dependency checks and status transitions across the entire epic in sprint-status.yaml.

Why does my story execution workflow require pre-flight validation and cascade impact checks?▼

Pre-flight validation and cascade impact checks are required to minimize drift from project conventions. They enforce code style mandates and verify that implementation changes do not cause unintended downstream issues.

Related Skills

Explore More Software Engineering Skills→
ImaginerLabsImaginerLabs

bmad-sprint-planning

Generate sprint-status.yaml from epic and story markdown files.

Official
Advanced
lorenzogmlorenzogm
15

bmad-retrospective

Analyze project artifacts to conduct structured post-epic retrospective reviews.

Community
Advanced
EmergenceAIEmergenceAI
2

code-review

Review branches, commits, PRs, or files with parallel agents.

Official
Advanced
mschuerigmschuerig

bmad-dev-story

Execute end-to-end story implementation from spec loading through review.

Community
Advanced