plan-stories

Convert PRDs into executable stories.json for Claude's agent pipeline.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/SyloRei/claude-godmode --skill plan-stories-sylorei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-stories
Source: https://github.com/SyloRei/claude-godmode/tree/main/skills/plan-stories
Command: npx skills add https://github.com/SyloRei/claude-godmode --skill plan-stories-sylorei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert PRDs into executable stories.json to drive the Claude agent pipeline, turning high-level product goals into actionable execution steps for automated planning and delivery.

Core Features & Use Cases

  • Converts PRDs from .claude-pipeline/prds/ into a stories.json payload consumable by the /execute workflow.
  • Auto-detects project quality gates (typecheck, lint, test, build) by inspecting project configuration files and scripts.
  • Ensures .claude-pipeline/ is gitignored and supports archiving previous runs for branch changes.
  • Produces a ready-to-run plan of US- stories with dependencies, branchName, prdSource, and maxParallel for safe parallel execution.

Quick Start

Place a PRD in .claude-pipeline/prds/ and run /plan-stories to generate a ready-to-run stories.json.

Frequently Asked Questions about plan-stories

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

FAQPage Schema
How do I convert a PRD into executable stories for automated planning?

To convert a PRD into executable stories, place the document in .claude-pipeline/prds/ and run the pipeline command. It generates a stories.json file containing actionable US- stories with dependencies for downstream orchestration.

What is a stories.json file and how does it drive an agent pipeline?

A stories.json file is a structured execution plan containing branchName, prdSource, maxParallel, and qualityGates. It drives an agent pipeline by providing sequential or parallel US- stories that downstream orchestration commands consume for automated delivery.

How do I auto-detect project quality gates like typecheck and lint for pipeline stories?

Auto-detecting project quality gates like typecheck and lint happens by inspecting project configuration files and scripts during PRD conversion. The generated stories.json automatically includes these detected gates to ensure execution meets project standards.

Does the pipeline execution workflow support parallel stories?

Yes, pipeline execution supports parallel stories by using the maxParallel parameter in the stories.json output. This defines the safe parallel execution limit for the generated US- stories during downstream orchestration.

Why does my pipeline archive previous runs when switching feature branches?

Archiving previous runs when switching feature branches prevents context collision and keeps the workspace clean. The pipeline automatically archives prior executions to ensure the new stories.json reflects the current branch state accurately.

Do I need to manually add .claude-pipeline to gitignore?

No, you do not need to manually add .claude-pipeline to gitignore. The PRD-to-stories conversion process automatically ensures the .claude-pipeline directory is gitignored to prevent committing pipeline artifacts to version control.