Agent skill
ralph-specum-design
This skill should be used only when the user explicitly asks to use `$ralph-specum-design`, or explicitly asks Ralph Specum in Codex to run the design phase.
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-design
Metadata
Additional technical details for this skill
- action
- design
- surface
- helper
SKILL.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
- Resolve the active spec. If none exists, stop.
- Require
requirements.md. Readresearch.mdwhen present,.progress.md, and current state. - Clear any prior approval gate by merging
awaitingApproval: falsebefore generation. - Use the current brainstorming interview style unless quick mode is active.
- Delegate design generation to an
architect-reviewersub-agent. Pass requirements, research, and interview context. The sub-agent writesdesign.md. Do NOT write design.md yourself. - Read the sub-agent's output and validate it exists.
- Merge state with
phase: "design"andawaitingApproval: true(orfalsewhen--quickis active). - Update
.progress.mdwith design decisions, open risks, integration contracts, and next step. - 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, namedesign.mdand summarize the design briefly. - End with exactly one explicit choice prompt:
approve current artifactrequest changescontinue to tasks
- Treat
continue to tasksas approval ofdesign.md.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
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.
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.
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.
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.
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.
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.
Didn't find tool you were looking for?