skills.rest
anderson-0
anderson-0COMMUNITY
Explore all skills by this author →
GitHub

dev-story

Execute software story implementation workflows from prepared development specifications.

4|2|Updated Apr 1, 2026
Search Tags:#testing#software development#code changes#review process#story implementation#sprint workflow
One-click install
npx skills add https://github.com/anderson-0/mighty-powers --skill dev-story-anderson-0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/anderson-0/mighty-powers/tree/main/skills/dev-story
Command: npx skills add https://github.com/anderson-0/mighty-powers --skill dev-story-anderson-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers complete structured software stories consistently by following a context-aware implementation workflow, reducing missed requirements, incomplete tasks, and inconsistent delivery.

Core Features & Use Cases

  • Story-Driven Implementation: Executes development tasks from prepared story specification files while preserving required story tracking fields.
  • Validation and Completion Gates: Guides implementation through testing, verification, file tracking, and definition-of-done checks before review readiness.
  • Use Case: A development team can use this Skill to implement a sprint story from a backlog file, update progress records, add tests, and prepare the completed work for code review.

Quick Start

Use the dev-story skill to implement the next ready-for-development story in the sprint plan.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I implement a sprint story from a backlog file while ensuring no requirements are missed?▼

Story implementation from a backlog file requires a structured workflow that preserves tracking fields and validates tasks against specifications. This ensures consistent delivery by guiding development through coding, testing, and completion gates before review.

What is the best way to manage code changes and workflow state during story implementation?▼

Managing code changes during story implementation involves strict workflow state management and continuous file tracking. This approach updates progress records systematically, ensuring that definition-of-done checks and validation gates are met safely.

How do I prepare completed development tasks for the code review process?▼

Preparing development tasks for the code review process requires passing validation and completion gates. This involves executing tests, verifying definition-of-done criteria, and updating story tracking fields to confirm review readiness.

Do I need prepared development specifications to start story implementation?▼

Yes, story implementation requires prepared development specifications as input. The workflow executes tasks directly from these story specification files to apply context-aware coding, testing, and review continuation safely.

What validation gates are required before a software story is considered ready for review?▼

Validation gates for software story review readiness include test execution, file tracking updates, and definition-of-done checks. These gates ensure all coding tasks and progress records meet the structured workflow requirements before completion.

Related Skills

Explore More Software Engineering Skills→
devalexanderdazadevalexanderdaza

bmad-create-story

Generate implementation-ready BMAD story files from epics, PRD, architecture, and UX artifacts.

Community
Advanced
cowwoccowwoc
4

task-cleanup

Remove task branches and worktrees after merge to main.

Community
Intermediate
hanzlahabibhanzlahabib
2

rcode-dev-story

Implement approved story files with tests and two-stage automated review.

Community
Advanced
summarybotngsummarybotng
2

github-project-management

Automates GitHub project management with AI swarm coordination.

Official
Advanced