ralph-specum-start
ralph-specum-start initializes or resumes a specification-driven development workflow within the Ralph Specum system. It parses user intent to identify or create a spec, resolves its location, initializes state tracking with phases and iteration limits, and sets up progress documentation. Use this skill when explicitly requested to start a new spec, resume an existing one, or begin work on a named specification goal.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-start && cp -r /tmp/ralph-specum-start/plugins/ralph-specum-codex/skills/ralph-specum-start ~/.claude/skills/ralph-specum-startSKILL.md
# Ralph Specum Start Use this for the `start` and `new` entrypoints. ## Contract - Read `.claude/ralph-specum.local.md` when present - Default specs root is `./specs` - Keep `.current-spec` in the default specs root - Keep the standard Ralph files stable - Merge `.ralph-state.json`. Do not replace the full object ## Action 1. Parse explicit name, goal, `--quick`, commit flags, optional specs root, and optional `--tasks-size fine|coarse`. 2. Resolve the target by explicit path, exact name, or `.current-spec`. 3. If the same name exists in multiple configured roots, stop and require a full path. 4. Check active epic context from `specs/.current-epic` when no explicit spec was chosen. 5. For large or cross-cutting goals, route to triage instead of forcing a single spec. 6. `new` is an alias here. Create the spec directory if needed. 7. Initialize or merge state with: - `source: "spec"` - `name` - `basePath` - `phase: "research"` - `taskIndex: 0` - `totalTasks: 0` - `taskIteration: 1` - `maxTaskIterations: settings default or 5` - `globalIteration: 1` - `maxGlobalIterations: 100` - `commitSpec: settings auto_commit_spec or true` - `relatedSpecs: []` - `awaitingApproval: true` when the run will stop after setup and wait for explicit direction - `awaitingApproval: false` when quick mode or explicit autonomy will continue without pausing - preserve or set `quickMode` - preserve or set `granularity` when `--tasks-size` was supplied - preserve or set `epicName` when starting from an epic suggestion 8. Update `.current-spec`. 9. Write `.progress.md` with goal, current phase, next step, blockers, learnings, and skill discovery results when used. 10. On resume, prefer `tasks.md` and present files over stale state when they disagree. 11. In quick mode, generate missing artifacts in order, skip normal approval pauses, and continue into implementation in the same run. 12. **Without quick mode or explicit autonomy: STOP HERE after setup. Do NOT proceed to research. Wait for the user to explicitly ask to continue.** This is non-negotiable. ## Branch Isolation - If the user wants isolation, offer a feature branch in place or a worktree with a feature branch. - If a worktree is created, stop after creation and ask the user to continue from that worktree. ## Response Handoff - After creating or resuming the spec, name the resolved spec path and summarize the current state briefly. - End with exactly one explicit choice prompt: - `request changes` - `continue to research` - Do not run research until the user explicitly asks to continue or explicitly asked for quick or autonomous flow.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
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.
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.