[GH-ISSUE #154] Feature request: Add --plan-only flag to `ralph plan` #58

New issue

Closed

opened 2026-02-27 10:21:59 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 10:21:59 +03:00

Owner

Originally created by @alexfosterinvisible on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/mikeyobrien/ralph-orchestrator/issues/154

Summary

ralph plan currently runs a full autonomous PDD-to-code pipeline, immediately diving into implementation after planning. There's no way to stop at the planning phase.

Problem

When running:

ralph plan "Write PDD plan: verify that the jsonl file is by itself enough to specify a run..."

The agent:

Creates planning documents (good) ✓
Immediately starts running Docker containers, tests, and scripts (unexpected) ✗

Users expect ralph plan to stop after generating planning artifacts (requirements.md, design.md, implementation-plan.md) and wait for approval before any implementation.

Current Workarounds

Use spec-driven preset which has approval gates between phases
Add explicit constraints to prompt: "DO NOT IMPLEMENT, PLANNING ONLY, emit LOOP_COMPLETE after documents"

Neither is ideal - the command name plan implies planning-only behavior.

Proposed Solution

Add --plan-only (or --no-implement) flag to ralph plan:

ralph plan --plan-only "Add user authentication"
# Creates specs/user-authentication/{requirements,design,implementation-plan}.md
# Emits LOOP_COMPLETE after documents are written
# Does NOT proceed to implementation

Alternative

Make ralph plan default to planning-only, with --execute or --full-pipeline to opt into the current behavior.

Environment

ralph version: 2.4.3
Backend: claude

Filed via Claude Code

Originally created by @alexfosterinvisible on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/mikeyobrien/ralph-orchestrator/issues/154 ## Summary `ralph plan` currently runs a full autonomous PDD-to-code pipeline, immediately diving into implementation after planning. There's no way to stop at the planning phase. ## Problem When running: ```bash ralph plan "Write PDD plan: verify that the jsonl file is by itself enough to specify a run..." ``` The agent: 1. Creates planning documents (good) ✓ 2. Immediately starts running Docker containers, tests, and scripts (unexpected) ✗ Users expect `ralph plan` to **stop after generating planning artifacts** (`requirements.md`, `design.md`, `implementation-plan.md`) and wait for approval before any implementation. ## Current Workarounds 1. **Use `spec-driven` preset** which has approval gates between phases 2. **Add explicit constraints to prompt**: "DO NOT IMPLEMENT, PLANNING ONLY, emit LOOP_COMPLETE after documents" Neither is ideal - the command name `plan` implies planning-only behavior. ## Proposed Solution Add `--plan-only` (or `--no-implement`) flag to `ralph plan`: ```bash ralph plan --plan-only "Add user authentication" # Creates specs/user-authentication/{requirements,design,implementation-plan}.md # Emits LOOP_COMPLETE after documents are written # Does NOT proceed to implementation ``` ## Alternative Make `ralph plan` default to planning-only, with `--execute` or `--full-pipeline` to opt into the current behavior. ## Environment - ralph version: 2.4.3 - Backend: claude --- Filed via Claude Code

kerem closed this issue

2026-02-27 10:22:00 +03:00

kerem commented

2026-02-27 10:22:00 +03:00

Author

Owner

@mikeyobrien commented on GitHub (Feb 5, 2026):

Unintended consequence of a prompt change. Hopefully the latest PR fixes things

@mikeyobrien commented on GitHub (Feb 5, 2026): Unintended consequence of a prompt change. Hopefully the latest PR fixes things