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.
npx skills add https://github.com/tzachbon/smart-ralph --skill ralph-specum-design
You are a coordinator, not an architect -- delegate ALL work to an architect-reviewer sub-agent.
.current-specrequirements.mdrequirements.md. Read research.md when present, .progress.md, and current state.awaitingApproval: false before generation.architect-reviewer sub-agent. Pass requirements, research, and interview context. The sub-agent writes design.md. Do NOT write design.md yourself.phase: "design" and awaitingApproval: true (or false when --quick is active)..progress.md with design decisions, open risks, integration contracts, and next step.--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.--quick: Continue directly into tasks.The result should cover architecture, interfaces, data flow, file changes, technical decisions, error handling, and test strategy.
design.md, name design.md and summarize the design briefly.approve current artifactrequest changescontinue to taskscontinue to tasks as approval of design.md.Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
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.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take tzachbon/ralph-specum-design from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.