ralph-specum-tasks
The ralph-specum-tasks Claude Code skill coordinates task planning for the Ralph Specum workflow by delegating work to a sub-agent task-planner. It resolves the active specification, validates required documentation files, clears approval gates, respects task granularity settings, and generates a structured tasks.md file with atomic tasks, success criteria, and verification commands. Use this skill when explicitly requested via the `$ralph-specum-tasks` command or when Ralph Specum in Codex needs to execute the tasks phase of project planning.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-tasks && cp -r /tmp/ralph-specum-tasks/plugins/ralph-specum-codex/skills/ralph-specum-tasks ~/.claude/skills/ralph-specum-tasksSKILL.md
# Ralph Specum Tasks You are a **coordinator, not a task planner** -- delegate ALL work to a `task-planner` sub-agent. ## Contract - Resolve the active spec by explicit path, exact name, or `.current-spec` - Require `requirements.md` and `design.md` - Merge state fields only - Keep the Ralph disk contract unchanged ## Action 1. Resolve the active spec. If none exists, stop. 2. Require `requirements.md` and `design.md`. Read `research.md` when present, `.progress.md`, and current state. 3. Clear any prior approval gate by merging `awaitingApproval: false` before generation. 4. Respect `granularity` from state. Allow `--tasks-size fine|coarse` to override it. In quick mode, default unset granularity to `fine`. 5. Use the current brainstorming interview style unless quick mode is active. 6. **Delegate** task planning to a `task-planner` sub-agent. Pass requirements, design, research, and interview context. The sub-agent writes `tasks.md`. Do NOT write tasks.md yourself. 7. Read the sub-agent's output and validate it exists. 8. Count tasks and merge state with: - `phase: "tasks"` - `awaitingApproval: true` (or `false` when `--quick` is active) - `taskIndex: first incomplete or totalTasks` - `totalTasks: counted tasks` 9. Update `.progress.md` with the phase breakdown, next milestone, blockers, next step, chosen granularity, and verification strategy. 10. If spec commits are enabled, commit only the spec artifacts. ### Stop Behavior - **Without `--quick`**: STOP HERE. Display the walkthrough summary and approval prompt. Do NOT continue to implementation. Wait for the user to explicitly approve and request the next phase. - **With `--quick`**: Review quickly, then continue directly into implementation. ## Output Shape Use atomic tasks with exact file targets, explicit success criteria, verification commands, and commit messages. Preserve POC-first ordering. Support `[P]` markers for safe parallel work, `[VERIFY]` checkpoints, and VE tasks when end-to-end verification is part of the plan. ## Response Handoff - After writing `tasks.md`, name `tasks.md` and summarize the task plan briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to implementation` - Treat `continue to implementation` as approval of `tasks.md`.
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.