Menu
Spec-driven development workflow for building features with research, requirements, design, and task phases
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to delegate implementation tasks to workers via Codex MCP or Task sub-agents. Use when executing tasks that require code implementation.
Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
Detect fix vs add goals, diagnose failures before work, verify fixes after. Ensures "fix X" specs actually fix X.
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
4-layer verification system for task completion. Use when verifying that a task has been fully completed before marking it done.
| name | spec-workflow |
| description | Spec-driven development workflow for building features with research, requirements, design, and task phases |
Use these commands when user wants to:
/ceo-ralph:start [name] [goal] - Start or resume a spec (smart entry point)/ceo-ralph:new <name> [goal] - Create new spec and begin research/ceo-ralph:research - Run research phase/ceo-ralph:requirements - Generate requirements from research/ceo-ralph:design - Generate technical design/ceo-ralph:tasks - Generate implementation tasks/ceo-ralph:implement - Start autonomous task execution/ceo-ralph:status - Show all specs and progress/ceo-ralph:switch <name> - Change active spec/ceo-ralph:cancel - Cancel active execution/ceo-ralph:help - Show plugin help