speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Show help for Ralph Specum plugin commands and workflow.
> /plugin marketplace add tzachbon/smart-ralphHow it fires
How this command gets triggered: by you, by Claude, or both.
/helpContext preview
What this command does when you run it.
Show help for Ralph Specum plugin commands and workflow.
description: Show help for Ralph Specum plugin commands and workflow.
Ralph Specum is a spec-driven development plugin that guides you through research, requirements, design, and task generation phases, then executes tasks autonomously with fresh context per task.
| Command | Description | |---------|-------------| | `/ralph-specum:start [name] [goal]` | Smart entry point: resume or create new | | `/ralph-specum:new <name> [goal]` | Create new spec and start research | | `/ralph-specum:research` | Run/re-run research phase | | `/ralph-specum:requirements` | Generate requirements (approves research) | | `/ralph-specum:design` | Generate design (approves requirements) | | `/ralph-specum:tasks` | Generate tasks (approves design) | | `/ralph-specum:prototype [--resume ID \| --cancel ID \| --quick]` | Run, resume, or cancel optional prototype evidence | | `/ralph-specum:implement` | Start execution loop (approves tasks) | | `/ralph-specum:status` | Show all specs and progress | | `/ralph-specum:switch <name>` | Change active spec | | `/ralph-specum:cancel` | Safely cancel active work; source is preserved | | `/ralph-specum:feedback [message]` | Submit feedback or report an issue | | `/ralph-specum:help` | Show this help |
/ralph-specum:new "my-feature"
|
v
[Research Phase] - Automatic on new
|
v (review research.md)
/ralph-specum:requirements
|
v (review requirements.md)
/ralph-specum:design
|
v (review design.md)
/ralph-specum:tasks
|
v (review tasks.md)
/ralph-specum:implement
|
v
[Task-by-task execution with fresh context]
|
v
Done!# Easiest: use start (auto-detects resume or new) /ralph-specum:start user-auth Add JWT authentication # Or resume an existing spec /ralph-specum:start # Manual workflow with individual commands: /ralph-specum:new user-auth Add JWT authentication /ralph-specum:requirements /ralph-specum:design /ralph-specum:tasks /ralph-specum:implement
Research and requirements may offer `continue to prototype`; declining continues the normal workflow. `/ralph-specum:prototype` is also available directly from research, requirements, design, tasks, or execution without changing the main phase.
Terminal records live under the resolved `<basePath>/prototypes/`. `status` shows active entries, review candidates, immutable finals, quarantines, blockers, return phase/task, and source disposition.
/ralph-specum:start [name] [goal] [--fresh] [--quick] [--commit-spec] [--no-commit-spec]
The `--commit-spec` setting is stored in `.ralph-state.json` and applies to local commits in all subsequent phases (research, requirements, design, tasks). It authorizes no remote prototype evidence action.
/ralph-specum:new <name> [goal] [--skip-research]
/ralph-specum:<phase> [spec-name]
Phase commands use the `commitSpec` setting from `.ralph-state.json` (set during `/ralph-specum:start`).
/ralph-specum:implement [--max-task-iterations 5]
Safe cancel deletes only execution state after every active prototype has a verified immutable `cancelled` record. It keeps the spec, prototype source, partial implementation, records, and local branches. Full spec removal requires a second confirmation naming the exact resolved directory; prototype paths and branches require separate confirmations.
Specs are stored in `./specs/` by default:
./specs/ ├── .current-spec # Active spec name (or full path for multi-dir) ├── my-feature/ │ ├── .ralph-state.json # Loop state (deleted on completion) │ ├── .progress.md # Progress tracking (persists) │ ├── research.md # Research findings │ ├── requirements.md # Requirements │ ├── design.md # Technical design │ ├── tasks.md # Implementation tasks │ └── prototypes/ # Immutable terminal prototype records
You can organize specs across multiple directories using the `specs_dirs` configuration.
Add `specs_dirs` to your settings file at `.claude/r
Spec-driven development with smart compaction. Claude Code plugin combining Ralph Wiggum loop with structured specification workflow.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Generate a custom checklist for the current feature based on user requirements.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
Execute the implementation plan by processing and executing all tasks defined in tasks.md
Execute the implementation planning workflow using the plan template to generate design artifacts.