From ceo
Performs two-stage code review: Stage 1 checks specification compliance to prevent scope creep, Stage 2 reviews code quality for maintainability.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ceo:two-stage-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Ensure code quality through a rigorous two-stage review process that catches both specification violations and maintainability issues.
Ensure code quality through a rigorous two-stage review process that catches both specification violations and maintainability issues.
Goal: Prevent over-building and under-building
Checklist:
Outcome: ✅ Compliant or ❌ Non-compliant with specific issues
Goal: Ensure maintainability and clarity
Checklist:
Outcome: ✅ Approved or ❌ Needs improvement with specific issues
Implementation → Stage 1 Review → ❌ Fix spec issues → Repeat Stage 1
→ ✅ Pass → Stage 2 Review → ❌ Fix quality issues → Repeat Stage 2
→ ✅ Pass → Complete
This skill is automatically invoked by the CEO workflow during Phase 4 (Development) after each subtask completion.
npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-2 --plugin pyinx-ceo-skills-pluginReviews implementation against spec requirements and code quality standards using a two-pass workflow. Useful for validating task completion.
Orchestrates two-stage code review: spec compliance against story acceptance criteria first, then code quality. For quantum-loop pipeline after implementation or standalone via git diffs.
Two-pass code review: first against the approved spec/plan, then quality across correctness, readability, architecture, security, and performance. Use after implementation tests pass or before merging.