skills.rest
LumenWipe
LumenWipeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dev-story

Implement software stories from specifications with task tracking and validation.

3|1|Updated May 12, 2026
Search Tags:#software development#test-driven development#acceptance criteria#code validation#story implementation#sprint tracking#review handoff
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill dev-story-lumenwipe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill dev-story-lumenwipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined workflow for implementing software stories from complete specifications, preventing skipped tasks, incomplete acceptance criteria, undocumented changes, and unvalidated code.

Core Features & Use Cases

  • Story Discovery: Finds the next ready-for-development story or uses a provided story path.
  • Guided Implementation: Loads project context, tracks sprint status, follows tasks in order, and applies a red-green-refactor development cycle.
  • Validation and Handoff: Creates and runs tests, checks quality gates, updates implementation records and file lists, and marks completed stories ready for review.
  • Use Case: Give the Skill a context-filled user authentication story, and it will implement the requested tasks, validate the acceptance criteria, document the changes, and update the story status for review.

Quick Start

Ask the AI to dev this story and provide the path to the context-filled story specification.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I implement software stories while tracking acceptance criteria and sprint status?▼

Software story implementation is driven by loading project context and following a guided workflow that tracks sprint status, executes tasks in order, and validates acceptance criteria. This approach applies a red-green-refactor cycle to ensure disciplined delivery.

What is test-driven development for story implementation and how does it handle code validation?▼

Test-driven development for story implementation involves writing tests first, running them to confirm failure, implementing code to pass tests, and refactoring. Code validation occurs by creating and running tests against acceptance criteria before marking stories ready for review.

Do I need a complete story file and project configuration to start story implementation?▼

Yes, story implementation requires a complete story file and project configuration. You must also provide access to the repository's testing and customization workflows to validate acceptance criteria and update implementation records correctly.

What's the best way to automate story discovery for sprint development workflows?▼

Automating story discovery involves configuring the workflow to find the next ready-for-development story automatically or using a provided story path. This ensures sprint development proceeds sequentially without missing context-filled specifications.

How does review handoff work after completing test-driven implementation?▼

Review handoff works by updating implementation records and file lists after running tests and checking quality gates. The workflow then marks completed stories as ready for review, ensuring all changes are documented and validated.

Why does code validation fail when acceptance criteria are incomplete during story implementation?▼

Code validation fails when acceptance criteria are incomplete because the workflow checks quality gates against the provided story specification. Skipping criteria prevents the system from verifying that tasks are fully implemented and ready for review handoff.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

bmad-dev-story

Automate end-to-end story implementation by loading context and executing tasks.

Community
Advanced
wsmanwsman
18

story-done

Verify development story completion against acceptance criteria and governance artifacts.

Community
Advanced
devalexanderdazadevalexanderdaza

bmad-dev-story

Automate end-to-end user story implementation from structured spec files.

Community
Advanced
dorriodorrio

ln-522-manual-tester

Execute bash scripts in tests/manual/ to validate Story AC.

Community
Intermediate