Two stage review
This skill should be used after completing development tasks. Performs two-stage code review: Stage 1 verifies specification compliance (prevents scope creep), Stage 2 reviews code quality (ensures maintainability).From its SKILL.md
npx -y skills add pyinx/ceo-skills-plugin --skill two-stage-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
Two-Stage Code Review
Purpose
Ensure code quality through a rigorous two-stage review process that catches both specification violations and maintainability issues.
Process
Stage 1: Specification Compliance Review
Goal: Prevent over-building and under-building
Checklist:
- ✅ All required features implemented (no missing functionality)
- ❌ No unauthorized features added (no scope creep)
- 📋 API design matches architecture document
- 📋 Data model matches specifications
- 📋 User stories fully satisfied
Outcome: ✅ Compliant or ❌ Non-compliant with specific issues
Stage 2: Code Quality Review
Goal: Ensure maintainability and clarity
Checklist:
- 📐 Clear variable naming
- 📐 Single responsibility functions
- 🔧 No code duplication
- 🔧 Modular design
- 🧪 Adequate test coverage
- ⚡ No obvious performance issues
- 🛡️ Input validation
- 🛡️ Error handling
Outcome: ✅ Approved or ❌ Needs improvement with specific issues
Review Loop
Implementation → Stage 1 Review → ❌ Fix spec issues → Repeat Stage 1
→ ✅ Pass → Stage 2 Review → ❌ Fix quality issues → Repeat Stage 2
→ ✅ Pass → Complete
Usage
This skill is automatically invoked by the CEO workflow during Phase 4 (Development) after each subtask completion.