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.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install tzachbon-smart-ralph-ralph-specum-design
Repository
Skill path: platforms/codex/skills/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.
Open repositoryBest for
Primary workflow: Design Product.
Technical facets: Full Stack, Designer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: tzachbon.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install ralph-specum-design into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/tzachbon/smart-ralph before adding ralph-specum-design to shared team environments
- Use ralph-specum-design for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: ralph-specum-design description: 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. metadata: surface: helper action: design --- # Ralph Specum Design Use this for the design phase. ## 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. Write or rewrite `design.md`. 6. Merge state with `phase: "design"` and `awaitingApproval: true`. 7. Update `.progress.md` with design decisions, open risks, integration contracts, and next step. 8. If spec commits are enabled, commit only the spec artifacts. 9. In quick mode, 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`.