story-execution

Implement the next unpassed user story from .ralf/prd.json within a Ralf loop.

4|2|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/anis-marrouchi/ralf --skill story-execution-anis-marrouchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-execution
Source: https://github.com/anis-marrouchi/ralf/tree/main/skills/story-execution
Command: npx skills add https://github.com/anis-marrouchi/ralf --skill story-execution-anis-marrouchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the implementation of a single user story within a Ralf iteration, ensuring consistent adherence to PRD criteria and progress tracking.

Core Features & Use Cases

  • Pre-implementation checks: verify PRD story details, target branch, and current iteration status.
  • Implementation cadence: execute acceptance criteria precisely, follow existing code conventions, and keep changes scoped.
  • Verification & logging: run typecheck, lint, tests if applicable, commit changes, update .ralf/prd.json, and append learnings to .ralf/progress.txt.

Quick Start

Follow the story-execution flow to implement the next unpassed story from .ralf/prd.json in the current Ralf loop.

Frequently Asked Questions about story-execution

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

FAQPage Schema
How do I automate user story implementation from a PRD in iterative loops?

User story implementation is automated by selecting the next unpassed story from PRD-defined acceptance criteria, translating them into code, running typechecks, and committing updates. This ensures consistent adherence to project conventions and tracks progress.

What is the best way to track progress after executing acceptance criteria?

Progress tracking is handled by updating the PRD file and appending iteration learnings to a progress log. After implementation and verification, changes are committed and the status is updated to reflect the completed acceptance criteria.

How do I ensure code conventions are followed during story execution?

Code conventions are maintained by scoping changes precisely to the acceptance criteria and verifying the implementation through typecheck, lint, and tests before committing. Pre-implementation checks also verify target branch and iteration status.

Can I use story-execution without prior pre-implementation checks?

Pre-implementation checks are required to verify PRD story details, target branch, and current iteration status. Running story execution without these checks risks inconsistent implementation and missing PRD criteria adherence.

Why does story execution fail if the PRD story details are missing?

Story execution fails because it relies on PRD-defined acceptance criteria to translate requirements into code. Missing story details prevent the loop from selecting the next unpassed story and applying the necessary pre-implementation checks.

Does story-execution work with version control for committing changes?

Version control is integrated into the post-implementation phase. After typechecks and tests pass, the skill commits the scoped changes directly to the target branch and updates the iteration progress logs accordingly.