ralph-specum-design
The ralph-specum-design skill coordinates the design phase of the Ralph Specum workflow by delegating architecture work to a sub-agent reviewer. It resolves the active specification, validates required documentation, clears approval gates, and orchestrates generation of a design.md artifact that covers architecture, interfaces, data flow, and technical decisions. Use this skill only when explicitly requested by the user or when Ralph Specum in Codex is directed to run the design phase, typically after requirements have been established and before task implementation begins.
git clone --depth 1 https://github.com/tzachbon/smart-ralph /tmp/ralph-specum-design && cp -r /tmp/ralph-specum-design/plugins/ralph-specum-codex/skills/ralph-specum-design ~/.claude/skills/ralph-specum-designSKILL.md
# Ralph Specum Design You are a **coordinator, not an architect** -- delegate ALL work to an `architect-reviewer` sub-agent. ## Contract - Resolve the active spec by explicit path, exact name, or `.current-spec` - Require `requirements.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`. Read `research.md` when present, `.progress.md`, and current state. 3. Clear any prior approval gate by merging `awaitingApproval: false` before generation. 4. Use the current brainstorming interview style unless quick mode is active. 5. **Delegate** design generation to an `architect-reviewer` sub-agent. Pass requirements, research, and interview context. The sub-agent writes `design.md`. Do NOT write design.md yourself. 6. Read the sub-agent's output and validate it exists. 7. Merge state with `phase: "design"` and `awaitingApproval: true` (or `false` when `--quick` is active). 8. Update `.progress.md` with design decisions, open risks, integration contracts, and next step. 9. 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 tasks. Wait for the user to explicitly approve and request the next phase. - **With `--quick`**: Continue directly into tasks. ## Output Shape The result should cover architecture, interfaces, data flow, file changes, technical decisions, error handling, and test strategy. ## Response Handoff - After writing `design.md`, name `design.md` and summarize the design briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to tasks` - Treat `continue to tasks` as approval of `design.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.