Agent skill

ralph-specum-implement

This skill should be used only when the user explicitly asks to use `$ralph-specum-implement`, or explicitly asks Ralph Specum in Codex to run implementation for approved tasks, quick mode, or an explicit continue request.

Stars 278
Forks 15

Install this agent skill to your Project

npx add-skill https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum-codex/skills/ralph-specum-implement

Metadata

Additional technical details for this skill

action
implement
surface
helper

SKILL.md

Ralph Specum Implement

You are a coordinator, not an executor -- delegate each task to a spec-executor sub-agent.

Contract

  • Resolve the active spec by explicit path, exact name, or .current-spec
  • Require tasks.md
  • Recompute task counts from disk before execution
  • Merge state fields only
  • Remove .ralph-state.json only when all tasks are complete and verified

Action

  1. Resolve the active spec. If none exists, stop.
  2. Require tasks.md. Read .progress.md, current state, and current task markers.
  3. Recompute task counters from disk: total, completed, and next_index.
  4. Merge state for execution:
    • phase: "execution"
    • awaitingApproval: false
    • totalTasks: total
    • taskIndex: next_index
    • preserve taskIteration, maxTaskIterations, globalIteration, maxGlobalIterations, commitSpec, and relatedSpecs
  5. Delegate each task to a spec-executor sub-agent. Pass the task description, file targets, success criteria, and context from .progress.md. The sub-agent implements the task and outputs TASK_COMPLETE. Do NOT implement tasks yourself. Execute tasks in order until complete or blocked.
  6. [P] tasks may batch only when file sets do not overlap and verification is independent.
  7. [VERIFY] tasks stay in the same run and must produce explicit verification evidence.
  8. Marker syntax must be explicitly present in tasks.md. If markers are absent, treat tasks as non-batchable by default.
  9. VE tasks are valid quality tasks when the spec includes autonomous end-to-end verification.
  10. Native task sync metadata should be preserved when present.
  11. After each task or safe batch:
  • mark the checkbox
  • update .progress.md
  • merge the state update
  • use the task Commit line unless commits were explicitly disabled
  1. On failure or interruption, persist the current state and stop with a resumable summary.
  2. On full completion, remove .ralph-state.json and report completion.

Resume Rules

  • Resume from the persisted task state when execution was already in progress.
  • If disk state and task checkboxes disagree, prefer tasks.md for completion and repair state to match.
  • If approval is still pending for tasks, stop and get approval unless quick mode or explicit user direction says to continue.

Expand your agent's capabilities with these related and highly-rated skills.

tzachbon/smart-ralph

MCP Integration

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.

278 15
Explore
tzachbon/smart-ralph

Command Development

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.

278 15
Explore
tzachbon/smart-ralph

Plugin Settings

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.

278 15
Explore
tzachbon/smart-ralph

Plugin Structure

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.

278 15
Explore
tzachbon/smart-ralph

Hook Development

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.

278 15
Explore
tzachbon/smart-ralph

Skill Development

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.

278 15
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results