rcode-dev-story

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

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-dev-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rcode-dev-story
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/4-implementation/rcode-dev-story
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-dev-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of implementing approved story files by guiding the full development workflow from requirements to review-ready completion.

Core Features & Use Cases

  • Story Execution: Reads an approved story, follows tasks in order, and implements only the scoped work requested.
  • Testing and Validation: Writes tests first, runs regressions, and verifies acceptance criteria before marking work complete.
  • Review-Ready Delivery: Updates the story record, resolves review follow-ups, syncs state, and performs two-stage automated review.
  • Use Case: A developer receives a ready-for-dev story and uses this Skill to code the feature, validate it, document the changes, and hand it off for human review.

Quick Start

Ask the rcode-dev-story skill to implement the approved story file you want completed and ready for review.

Frequently Asked Questions about rcode-dev-story

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

FAQPage Schema
How do I implement approved story files while following test-driven development?▼

Implement approved story files by executing acceptance criteria in strict task order, writing tests first, running regressions, and validating before marking work ready. This workflow automation enforces task-order fidelity and validation gates throughout story implementation.

What is the best way to automate code review and state synchronization during feature delivery?▼

Automate code review and state synchronization by performing a two-stage automated review, syncing state, and updating the story record after implementing acceptance criteria. This ensures review-ready delivery for feature workflows.

How do I resolve review follow-ups and remediation tasks for story implementation?▼

Resolve review follow-ups by executing the approved story file's remediation tasks in order, running validation gates, and syncing state before performing a final two-stage automated review to mark the work ready.

Does this story implementation workflow require prepared markdown files?▼

Yes, story implementation requires prepared story markdown files that contain approved acceptance criteria. The Skill reads these ready-for-dev files, implements the scoped work, updates the story record, and hands it off for human review.

When should I not use automated story execution for feature development?▼

Avoid automated story execution when your story files lack approved acceptance criteria or when tasks are not sequentially ordered. The workflow requires task-order fidelity, validation gates, and state synchronization to properly function during phase-based development.