Skip to content
cccskills
FreePublished on GitHub

ralph-specum-refactor

This skill should be used only when the user explicitly asks to use `$ralph-specum-refactor`, or explicitly asks Ralph Specum in Codex to revise spec artifacts after implementation learnings.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph
See how to install

Files included (2)

  • SKILL.md2.4 KB
  • agents/openai.yaml413 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Ralph Specum Refactor

You are a coordinator, not a refactor specialist -- delegate spec revision to a refactor-specialist sub-agent.

Contract

  • Resolve the active spec by explicit path, exact name, or .current-spec
  • Review files in order: requirements.md, design.md, tasks.md
  • Cascade downstream updates when upstream content changes
  • Reconcile activePrototypes and preserve unrelated refactor work

Action

  1. Resolve the target spec.
  2. Read .progress.md and existing spec files.
  3. Run prototype_records.py reconcile whenever .ralph-state.json exists, including when activePrototypes is empty, then run select-downstream --state "$BASE_PATH/.ralph-state.json" --target "$FILE" --path "$FILE" with the resolved basePath. Stop a file's refactor when its targetDecisions entry is not both proofAvailable: true and eligible: true, including an active blocker, stale dependency, approved-transfer overlap, or unavailable proof.
  4. When refactor returns to execution, restore taskIndex from the blocking entry's returnTaskIndex through merge_state.py before dispatch.
  5. Delegate spec revision to a refactor-specialist sub-agent. Pass .progress.md, existing spec files, and implementation learnings. The sub-agent identifies what changed, what stayed accurate, and what is obsolete. Do NOT revise spec files yourself.
  6. The sub-agent preserves newer Ralph concepts already expressed in the spec, including approval checkpoints, granularity choices, [P] tasks, [VERIFY] tasks, VE tasks, and epic constraints when relevant.
  7. The sub-agent updates files in order:
    • requirements.md
    • design.md
    • tasks.md
  8. If requirements changed, revisit design and tasks.
  9. If design changed, revisit tasks.
  10. Record the rationale and cascade decisions in .progress.md.

Response Handoff

  • After revising spec files, name the files that changed and summarize the updates briefly.
  • End with exactly one explicit choice prompt:
    • approve current artifact
    • request changes
    • continue to implementation
  • Treat continue to implementation as approval of the updated spec files.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Command Development

Free

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.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

communication-style

Free

Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

communication-style

Free

This skill should be used when generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

delegation-principle

Free

Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

Hook Development

Free

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.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

interview-framework

Free

This skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.

The English summary is being prepared. Showing the original description.

tzachbon/smart-ralph559Updated Sep 16, 2026

See all skills by tzachbon

Report a problem with this skill