rcode-create-story

Create dev-ready story files with BDD acceptance criteria from epic and architecture inputs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns backlog and architecture inputs into a complete, dev-ready story file so implementation starts with clear scope, acceptance criteria, and guardrails.

Core Features & Use Cases

  • Story Assembly: Builds a structured story from epic, PRD, architecture, sprint-status, and prior-story context.
  • Implementation Guardrails: Adds technical constraints, file-structure notes, testing expectations, and dependency awareness to reduce developer mistakes.
  • Use Case: Use it when you need the next backlog item prepared for development with BDD acceptance criteria, task breakdown, and project-specific context.

Quick Start

Ask the skill to create the next ready-for-dev story from the current sprint and project documents.

Frequently Asked Questions about rcode-create-story

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

FAQPage Schema
How do I create dev-ready stories from epics for sprint planning?

To create dev-ready stories, you assemble epic details, architecture constraints, and sprint status into a structured file with BDD acceptance criteria and implementation guardrails. This ensures development starts with clear scope and technical constraints.

What is BDD acceptance criteria and how does it apply to story creation?

BDD acceptance criteria define behavior-driven scenarios for validating story completion. When creating stories, applying BDD formatting ensures developers understand exact expected outcomes and testing expectations before implementation begins.

How to include architecture guardrails and dependency checks in story files?

Architecture guardrails and dependency checks are included during story assembly by extracting technical constraints and file-structure notes from architecture documents. This reduces developer mistakes by ensuring prior-work continuity and dependency awareness.

Can I generate a structured story file from PRD and backlog inputs automatically?

Yes, you can generate structured story files by processing PRD, backlog, and sprint tracking inputs. The output provides deterministic story formatting with task breakdown, technical constraints, and project-specific context for immediate developer handoff.

Does story creation work with prior-story continuity for backlog selection?

Story creation supports prior-story continuity by reusing previous work context during backlog selection. It checks dependencies and sprint status to ensure the next ready-for-dev story aligns with existing implementation progress.

What are the limitations of deterministic story formatting for developer handoff?

Deterministic story formatting relies entirely on the quality of epic, architecture, and sprint tracking inputs provided. If source documents lack detail or technical constraints are missing, the generated story file will reflect those gaps in scope and guardrails.