From ceo-ralph
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ceo-ralph:review-criteriaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill defines how the CEO (Claude) reviews outputs from Codex workers.
This skill defines how the CEO (Claude) reviews outputs from Codex workers.
Every Codex output must be reviewed across 5 dimensions:
Question: Did the worker do what was asked?
Checklist:
Fail Conditions:
Question: Does the output meet all acceptance criteria?
Process:
For each acceptance criterion in the task:
- [ ] AC-1: {criterion} → PASS/FAIL: {reason}
- [ ] AC-2: {criterion} → PASS/FAIL: {reason}
- [ ] AC-3: {criterion} → PASS/FAIL: {reason}
Criteria Met: {passed}/{total}
Fail Conditions:
Question: Is the code well-written?
| Aspect | Weight | Check |
|---|---|---|
| Patterns | High | Follows existing codebase patterns |
| Bugs | High | No obvious logical errors |
| Error Handling | Medium | Proper try/catch, null checks |
| Readability | Medium | Clear naming, reasonable complexity |
| Security | High | No obvious vulnerabilities |
Fail Conditions:
Question: Will this work with existing code?
Checklist:
Fail Conditions:
Question: Is the output complete and usable?
Checklist:
// TODO, // FIXME)... or ellipsis in codeFail Conditions:
| Completeness | Criteria | Quality | Integration | Decision |
|---|---|---|---|---|
| ✓ | ✓ | ✓ | ✓ | APPROVED |
| ✓ | ✓ | ✗ | ✓ | NEEDS_REVISION |
| ✓ | ✗ | ✓ | ✓ | NEEDS_REVISION |
| ✓ | ✓ | ✓ | ✗ | NEEDS_REVISION |
| ✗ | - | - | - | NEEDS_REVISION |
| - | ✗✗ | - | - | ESCALATE (if max retries) |
## Review: Task {id} - APPROVED ✓
All criteria met. Output is ready for verification.
**Summary**:
- Completeness: PASS
- Acceptance: {n}/{n} criteria met
- Quality: Good
- Integration: Compatible
## Review: Task {id} - NEEDS_REVISION ↻
Attempt {n} of {max}. Issues found:
**Issue 1**: {Specific issue}
- File: {path}
- Line: {number} (if applicable)
- Current: {what's wrong}
- Expected: {what's needed}
- Fix: {specific instruction}
**Issue 2**: {Specific issue}
- Fix: {specific instruction}
**Focus Areas for Retry**:
1. {Priority 1}
2. {Priority 2}
## Review: Task {id} - ESCALATE ⚠️
Max retries ({max}) reached or blocking issue found.
**Reason for Escalation**: {why}
**Attempts Summary**:
| Attempt | Issue | Feedback Given |
|---------|-------|----------------|
| 1 | {issue} | {feedback} |
| 2 | {issue} | {feedback} |
| 3 | {issue} | {feedback} |
**Options for User**:
1. Provide additional guidance and retry
2. Manually implement this task
3. Skip this task (if [OPTIONAL])
4. Modify requirements
When reviewing, compare against:
JavaScript/TypeScript:
React:
API/Backend:
| Task Type | Max Iterations | Escalate After |
|---|---|---|
| Standard | 3 | 3 failures |
| [CRITICAL] | 5 | 5 failures |
| [OPTIONAL] | 2 | Skip after 2 |
npx claudepluginhub dutstech/ceoralph --plugin ceo-ralphGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.