Ralph Plan

Interactive planning tools for defining product vision, roadmap, user stories, and tasks.

Canonical Rules

Use canonical atomic docs for shared planning rules instead of restating them:

• Naming/numbering/placement: @context/blocks/docs/naming-convention.md
• Subtask schema and ID allocation: @context/workflows/ralph/planning/subtask-spec.md

Execution Instructions

When this skill is invoked, check the ARGUMENTS provided:

If argument is vision:

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/vision-interactive.md (relative to project root). DO NOT proceed without reading this file first - it contains the full Socratic workflow you MUST follow.

After reading the workflow file, begin the session with:

---

"Let's work on clarifying your product vision. I'll ask questions to help you articulate what you're building and why.

To start: What problem are you trying to solve, and for whom?

(You can say 'done' at any point when you feel we've covered enough. I'll offer to save our progress incrementally as we go.)"

---

Then follow ALL phases in the workflow file you just read.

If argument is roadmap:

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/roadmap-interactive.md (relative to project root). DO NOT proceed without reading this file first - it contains the full Socratic workflow with ALL phases you MUST follow.

1. First, read docs/planning/VISION.md to understand the product vision
2. If no VISION.md exists, inform the user and suggest they run /ralph-plan vision first
3. Begin the session with:

---

"Let's work on your product roadmap. I've read your vision document and I'll ask questions to help translate it into actionable milestones.

To start: What's the most important thing users should be able to do in your first release?

(You can say 'done' at any point when you feel we've covered enough. I'll offer to save our progress incrementally as we define milestones.)"

---

Then follow ALL phases in the workflow file you just read. Do NOT skip phases or give shallow output.

If argument is stories (with optional milestone name):

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/stories-interactive.md (relative to project root). DO NOT proceed without reading this file first - it contains the full Socratic workflow you MUST follow.

1. First, read docs/planning/VISION.md and docs/planning/ROADMAP.md to understand the product context
2. If no VISION.md or ROADMAP.md exists, inform the user and suggest they run /ralph-plan vision and /ralph-plan roadmap first
3. If a milestone name was provided as a second argument (e.g., /ralph-plan stories my-milestone), use that milestone
4. If no milestone was provided, ask the user which milestone they want to create stories for
5. Begin the session with:

---

"Let's create user stories for the [milestone] milestone.

I've reviewed the roadmap - this milestone focuses on: [list key deliverables from ROADMAP.md]

To start: Who are the primary users that will benefit from these capabilities? What are they trying to accomplish?

(You can say 'done' at any point when you feel we've covered enough, or ask me to save a story when we've defined it well.)"

---

Then follow ALL phases in the workflow file you just read.

IMPORTANT - Incremental Saving: Save each story as it's well-defined:

• After each story is discussed and refined, offer to write it to a file
• Don't batch all stories at the end
• This protects against crashes/disconnects

If argument is tasks (with required story ID):

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/tasks-interactive.md (relative to project root). DO NOT proceed without reading this file first - it contains the full Socratic workflow you MUST follow.

1. A story ID must be provided as the second argument (e.g., /ralph-plan tasks STORY-001-auth)
2. If no story ID is provided, ask the user which story to create tasks for and list available stories
3. Find the story file in docs/planning/milestones/*/stories/<story-id>.md
4. If the story is not found, list available stories and ask for clarification
5. Read the story file to understand the user outcomes
6. Explore the codebase to understand existing patterns relevant to the story
7. Begin the session with:

---

"Let's create technical tasks for story [story-id].

I've read the story - it focuses on: [brief summary of narrative and key acceptance criteria].

Let me also explore the codebase to understand existing patterns..."

[Read relevant files/directories based on the story context]

"Based on the story and the codebase, here's what I see:

• [relevant existing code/patterns]
• [dependencies/integrations involved]

To start: Looking at the acceptance criteria, which capability should we tackle first? What's your thinking on the technical approach?

(You can say 'done' at any point when you feel we've covered enough, or ask me to save a task when we've defined it well.)"

---

Then follow ALL phases in the workflow file you just read.

IMPORTANT - Incremental Saving: Save each task as it's well-defined:

• After each task is discussed and refined, offer to write it to a file
• Don't batch all tasks at the end
• This protects against crashes/disconnects

If argument is tasks <story-id> --auto:

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/tasks-auto.md (relative to project root). DO NOT proceed without reading this file first - it contains the full auto-generation workflow.

1. A story ID must be provided (e.g., /ralph-plan tasks STORY-001-auth --auto)
2. Find the story file in docs/planning/milestones/*/stories/<story-id>.md
3. If the story is not found, report error and list available stories
4. Analyze the codebase for patterns relevant to the story
5. Generate task files automatically following the workflow

Auto mode outputs:

• Task files are created without interaction
• Summary reports what was generated
• No incremental saving prompts (all tasks saved at once)

If argument is tasks --milestone <name> --auto:

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/tasks-milestone.md (relative to project root). DO NOT proceed without reading this file first - it contains the parallel agent orchestration workflow.

1. A milestone name must be provided (e.g., /ralph-plan tasks --milestone ralph --auto)
2. Discover all stories in docs/planning/milestones/<name>/stories/
3. If no stories found, report error with available milestones
4. Follow canonical folder-local task numbering rules from @context/blocks/docs/naming-convention.md
5. Spawn parallel task-generator subagents (one per story)
6. Each agent generates tasks for its story independently
7. Report summary of all generated tasks

Parallelization benefits:

• Faster: Multiple stories processed concurrently
• Better quality: Smaller context per agent
• Consistent: Same patterns applied across all stories

If argument is tasks --file or tasks --text (alternative source):

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/tasks-from-source.md (relative to project root). DO NOT proceed without reading this file first - it contains the workflow for generating tasks from alternative sources.

1. An alternative source must be provided - one of:
   • --file <path> (e.g., /ralph-plan tasks --file ./spec.md)
   • --text <string> (e.g., /ralph-plan tasks --text "Add user auth")
2. Read the source and extract actionable items
3. Generate tasks following the template
4. Write to docs/planning/tasks/

Begin the session with:

---

"I'll generate tasks from the provided source.

Source: [file path / text description]

Let me read and analyze the source to extract requirements..."

---

Then follow ALL steps in the workflow file you just read.

If argument is subtasks --milestone or subtasks --story (hierarchy source):

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/subtasks-from-hierarchy.md (relative to project root). DO NOT proceed without reading this file first - it contains the parallel agent orchestration workflow.

CRITICAL - Append, Don't Overwrite: When writing subtasks.json, use appendSubtasksToFile() from tools/src/commands/ralph/config.ts. This function appends new subtasks to existing files instead of overwriting them. Never use saveSubtasksFile() directly for subtask planning - it destroys existing subtasks.

1. A hierarchy source must be provided:
   • --milestone <name> to process all tasks in the milestone
   • --story <path> to process all tasks linked to that story
2. Discover all tasks for the given scope
3. Spawn parallel agents (one per task) to generate subtasks
4. Aggregate results to docs/planning/milestones/<milestone>/subtasks.json using appendSubtasksToFile()

Begin the session with:

---

"I'll generate subtasks for all tasks in the [milestone/story].

Source: [milestone name / story path] Mode: Hierarchy-based (processing all tasks)

Let me discover the tasks and spawn parallel agents..."

---

Then follow ALL steps in the workflow file you just read.

If argument is subtasks with --file, --text, or --review-diary (alternative source):

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/subtasks-from-source.md (relative to project root). DO NOT proceed without reading this file first - it contains the full workflow you MUST follow.

CRITICAL - Append, Don't Overwrite: When writing subtasks.json, use appendSubtasksToFile() from tools/src/commands/ralph/config.ts. This function appends new subtasks to existing files instead of overwriting them. Never use saveSubtasksFile() directly for subtask planning - it destroys existing subtasks.

1. An alternative source must be provided - one of:
   • --file <path> (e.g., /ralph-plan subtasks --file ./review-findings.md)
   • --text <string> (e.g., /ralph-plan subtasks --text "Fix array bounds check")
   • --review-diary flag to parse logs/reviews.jsonl
2. Read the source and extract actionable items
3. Generate subtasks following the schema and sizing constraints from the workflow
4. Write to docs/planning/subtasks.json or specified milestone location using appendSubtasksToFile()

Begin the session with:

---

"I'll generate subtasks from the provided source.

Source: [file path / text / review diary]

Let me read and analyze the source to extract actionable items..."

---

Then follow ALL steps in the workflow file you just read.

If argument is subtasks --task (single task source):

MANDATORY FIRST STEP: Use the Read tool to read context/workflows/ralph/planning/subtasks-auto.md (relative to project root). DO NOT proceed without reading this file first.

CRITICAL - Append, Don't Overwrite: When writing subtasks.json, use appendSubtasksToFile() from tools/src/commands/ralph/config.ts. This function appends new subtasks to existing files instead of overwriting them. Never use saveSubtasksFile() directly for subtask planning - it destroys existing subtasks.

1. A task path is required via --task <path>
2. Read the task file to understand the implementation scope
3. Generate subtasks for that specific task
4. Write to appropriate subtasks.json location using appendSubtasksToFile()

Begin the session with:

---

"I'll generate subtasks for the specified task.

Task: [task path]

Let me read and analyze the task..."

---

Then follow ALL steps in the workflow file you just read.

If no argument or unknown argument:

Show the usage documentation below.

---

Usage

/ralph-plan <subcommand>

Subcommands

Subcommand	Description
vision	Start interactive vision planning session
roadmap	Start interactive roadmap planning session
stories	Start interactive stories planning session for a milestone
tasks	Start interactive tasks planning session for a story
subtasks	Generate subtasks from any source (file, text, or review diary)

Vision Planning

Start an interactive Socratic dialogue to help define and clarify product vision.

Invocation

/ralph-plan vision

What Happens

1. Begins a multi-turn conversation using the Socratic method
2. Guides you through exploring:
   • Product purpose and problem being solved
   • Target users using Jobs To Be Done framework
   • Key capabilities and differentiators
   • Current state vs future vision
3. Creates or updates docs/planning/VISION.md when ready

Important Notes

• This is interactive only - no auto mode exists for vision planning
• Vision planning requires human insight and decision-making
• You control the pace and can exit anytime by saying "done"
• The session can span multiple turns as needed

Roadmap Planning

Start an interactive Socratic dialogue to help define product milestones and roadmap.

Invocation

/ralph-plan roadmap

What Happens

1. Reads your existing VISION.md document (if it exists)
2. Begins a multi-turn conversation using the Socratic method
3. Guides you through exploring:
   • Scope and priority for first release
   • Tradeoffs and hard decisions
   • Dependency mapping between features
   • Milestone definition with outcomes
4. Creates or updates docs/planning/ROADMAP.md when ready

Important Notes

• Requires VISION.md to exist (run /ralph-plan vision first)
• Interactive mode available, auto mode available via roadmap-auto.md
• Milestones use outcome-based names, not version numbers
• No time estimates - focus on sequence and dependencies
• You control the pace and can exit anytime by saying "done"

Stories Planning

Start an interactive Socratic dialogue to help create user stories for a specific milestone.

Invocation

/ralph-plan stories [milestone-name]

What Happens

1. Reads your existing VISION.md and ROADMAP.md documents
2. If a milestone name is provided, uses that milestone
3. If no milestone is provided, asks which milestone to create stories for
4. Begins a multi-turn conversation using Socratic method with JTBD framework
5. Guides you through exploring:
   • Primary users and their context
   • Jobs to be done (functional, emotional, social)
   • Story scope and boundaries
   • Priority and sequencing
   • Tradeoffs and decisions
   • Acceptance criteria
6. Creates story files in docs/planning/milestones/<milestone>/stories/

Important Notes

• Requires VISION.md and ROADMAP.md to exist (run vision and roadmap planning first)
• Uses Jobs To Be Done (JTBD) framework for user-centered stories
• Stories focus on user outcomes, not technical implementation
• You control the pace and can exit anytime by saying "done"
• Can save stories incrementally during the session

Tasks Planning

Create technical tasks from stories. Three modes available:

Single Story Mode (Interactive, Supervised, or Headless)

/ralph-plan tasks <story-id>

What Happens:

1. Reads the specified story file to understand user outcomes
2. Explores the codebase to understand existing patterns relevant to the story
3. Begins a multi-turn conversation using Socratic method (or auto-generates in supervised/headless mode)
4. Creates task files in docs/planning/tasks/

Milestone Mode (Supervised or Headless)

aaa ralph plan tasks --milestone <name> --headless

What Happens:

1. Discovers all stories in docs/planning/milestones/<name>/stories/
2. Spawns parallel task-generator subagents (one per story)
3. Each agent analyzes its story and the codebase
4. Task files are generated concurrently for all stories
5. Reports summary of all generated tasks

Benefits:

• Faster: Parallel generation vs sequential
• Better quality: Smaller context per agent
• Consistent: Same patterns applied across stories

Important Notes

• Single story mode: Requires --story <id>
• Milestone mode: Requires --milestone <name> and one of --supervised or --headless
• Cannot combine --story and --milestone
• Tasks are linked to their parent story for traceability
• Focus is on technical implementation, not user outcomes
• References specific files and patterns from the codebase

Subtasks Planning

Generate subtasks from hierarchy (tasks in milestone/story) or alternative sources (file, text, review).

Source Types

Hierarchy Sources (scope = source):

Flag	Example	Meaning
--milestone	--milestone 003-ralph	All tasks in milestone → subtasks
--story	--story STORY-001	All tasks for that story → subtasks
--task	--task TASK-001	That task → subtasks

Alternative Sources:

Flag	Example	Meaning
--file	--file ./spec.md	File content → subtasks
--text	--text "Fix bug"	Text description → subtasks
--review-diary	--review-diary	Review diary findings → subtasks

Invocation

# Hierarchy sources (scope flags)
aaa ralph plan subtasks --milestone 003-ralph-workflow --headless
aaa ralph plan subtasks --story STORY-001 --headless
aaa ralph plan subtasks --task TASK-001 --headless

# Alternative sources (explicit flags)
aaa ralph plan subtasks --file ./review-findings.md
aaa ralph plan subtasks --text "Fix array bounds check"
aaa ralph plan subtasks --review-diary

# With sizing
aaa ralph plan subtasks --milestone 003-ralph --size small --headless

Optional Flags

• --size <mode> - Slice thickness: small, medium (default), large

What Happens

For hierarchy sources:

1. Discovers all tasks in the scope (milestone or story)
2. Spawns parallel agents (one per task)
3. Each agent generates subtasks for its task
4. Aggregates to docs/planning/milestones/<milestone>/subtasks.json

For alternative sources:

1. Reads the source (file content, text, or logs/reviews.jsonl)
2. Extracts actionable items from the source
3. Generates subtasks following schema and sizing constraints
4. Writes to docs/planning/subtasks.json or specified milestone location

Important Notes

• Hierarchy sources (--milestone, --story) are the primary way to generate subtasks
• Alternative sources bypass the planning hierarchy for ad-hoc use cases
• Each subtask should touch 1-3 files (not counting tests)
• Subtasks must be completable in 15-30 tool calls
• Subtask IDs use SUB-NNN and are milestone-scoped in the target queue (see @context/workflows/ralph/planning/subtask-spec.md)

CLI Equivalent

This skill provides the same functionality as:

aaa ralph plan vision
aaa ralph plan roadmap
aaa ralph plan stories --milestone <name>
# Tasks from hierarchy
aaa ralph plan tasks --story <story-id>           # Story → tasks
aaa ralph plan tasks --milestone <name> --headless # All stories in milestone → tasks
# Tasks from alternative sources
aaa ralph plan tasks --file ./spec.md             # File → tasks
aaa ralph plan tasks --text "Add auth"            # Text → tasks
# Subtasks from hierarchy
aaa ralph plan subtasks --milestone <name>        # All tasks in milestone → subtasks
aaa ralph plan subtasks --story <story-id>        # All tasks for story → subtasks
aaa ralph plan subtasks --task <task-id>          # Single task → subtasks
# Subtasks from alternative sources
aaa ralph plan subtasks --file ./spec.md          # File → subtasks
aaa ralph plan subtasks --text "Fix bug"          # Text → subtasks
aaa ralph plan subtasks --review-diary            # Review diary → subtasks

References

• Vision prompt: context/workflows/ralph/planning/vision-interactive.md
• Roadmap prompt: context/workflows/ralph/planning/roadmap-interactive.md
• Stories prompt: context/workflows/ralph/planning/stories-interactive.md
• Tasks prompt: context/workflows/ralph/planning/tasks-interactive.md
• Tasks milestone prompt: context/workflows/ralph/planning/tasks-milestone.md
• Tasks from source: context/workflows/ralph/planning/tasks-from-source.md
• Subtasks from hierarchy: context/workflows/ralph/planning/subtasks-from-hierarchy.md
• Subtasks from source: context/workflows/ralph/planning/subtasks-from-source.md
• Subtasks from task: context/workflows/ralph/planning/subtasks-auto.md
• Task generator agent: .claude/agents/task-generator.md