This skill should be used when the user asks about "ralph arguments", "quick mode", "commit spec", "max iterations", "ralph state file", "execution modes", "ralph loop", "coordinator behavior", "delegate to subagent", or needs guidance on Ralph plugin arguments, state management, delegation patterns, or execution loop behavior. Core behavioral skill for all Ralph Specum operations.
npx skills add https://github.com/tzachbon/smart-ralph --skill smart-ralph
Core skill for all Ralph plugins. Defines common arguments, execution modes, shared behaviors, and coordinator delegation rules.
All Ralph commands support these standard arguments:
| Argument | Short | Description | Default |
|----------|-------|-------------|---------|
| --quick | -q | Skip interactive phases, auto-generate artifacts, start execution immediately | false |
| --commit | -c | Commit and push spec/feature files after generation | true (normal), false (quick) |
| --no-commit | | Explicitly disable committing files | - |
| --max-task-iterations | -m | Max retries per failed task before stopping | 5 |
| --fresh | -f | Force new spec/feature, overwrite if exists | false |
Argument precedence: --no-commit > --commit > mode default.
awaitingApproval: true--quick)--commit to override)All Ralph plugins use .ralph-state.json for execution state. See references/state-file-schema.md for full schema.
Key fields: phase, taskIndex, totalTasks, taskIteration, maxTaskIterations, awaitingApproval.
When commitSpec is true:
chore(<plugin>): commit spec files before implementationWhen commitSpec is false:
Ralph Specum v3.0.0+ has a self-contained execution loop via the stop-hook. No external dependencies required.
Key signals:
TASK_COMPLETE - executor finished taskALL_TASKS_COMPLETE - coordinator ends loopWhen taskIteration > maxTaskIterations: block task, suggest manual intervention.
If state file missing/invalid: output error, suggest re-running implement command.
All Ralph plugins follow consistent branch strategy:
The main agent is a coordinator, not an implementer. Delegate all work to subagents.
| Work Type | Delegate To |
|-----------|-------------|
| Research | Research Team (parallel teammates) |
| Requirements | product-manager subagent |
| Design | architect-reviewer subagent |
| Task planning | task-planner subagent |
| Task execution | spec-executor subagent |
Quick mode still requires delegation.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take tzachbon/smart-ralph-smart-ralph from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.