two-stage-review

Name: two-stage-review
Availability: InStock
Author: pyinx

A comprehensive review of code quality and performance, ensuring alignment with specifications.

14|2|Updated Jan 19, 2026

Search Tags:#automation #specification #maintainability #quality-assurance #code-review #software-engineering #two-stage-review

Ready to run

npx skills add https://github.com/pyinx/ceo-skills-plugin --skill two-stage-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: two-stage-review
Source: https://github.com/pyinx/ceo-skills-plugin/tree/main/skills/two-stage-review
Command: npx skills add https://github.com/pyinx/ceo-skills-plugin --skill two-stage-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents scope creep and quality issues by enforcing a clean separation between specification compliance and code quality during post-development reviews.

Core Features & Use Cases

Stage 1 Review: verify specification compliance (no scope creep, API and data-model alignment)
Stage 2 Review: assess maintainability, naming clarity, modular design, and test coverage
Usage: integrated into the CEO workflow to automatically trigger after each development subtask

Quick Start

Trigger two-stage-review in the CEO workflow after completing a development subtask to ensure both specification alignment and code quality.

Frequently Asked Questions about two-stage-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a two-stage code review and how does it prevent scope creep?▼

A two-stage code review separates specification compliance from maintainability checks to prevent scope creep. Stage 1 verifies feature completeness and API alignment, while Stage 2 enforces modular design and naming clarity.

How do I automate code reviews for specification compliance and quality assurance?▼

Automate code reviews for specification compliance by triggering a two-pass review after development subtasks. This process automatically checks feature completeness, API compatibility, data-model alignment, and test coverage.

Does two-stage code review check for maintainability and test coverage?▼

Yes, two-stage code review checks for maintainability and test coverage during its second stage. It assesses single-responsibility functions, naming clarity, lack of duplication, input validation, error handling, and adequate test coverage.

When do I need a two-pass code review in software engineering?▼

You need a two-pass code review when completing development subtasks to ensure specification alignment and code quality. It is specifically designed to enforce a clean separation between feature completeness and maintainable code.

Can I integrate automated code review into a post-development workflow?▼

Yes, you can integrate automated code review into a post-development workflow. It is designed to trigger after subtasks in the CEO workflow to automatically enforce specification compliance and maintainable code quality.

What is the best way to verify API compatibility and data-model alignment after development?▼

The best way to verify API compatibility and data-model alignment is using a Stage 1 specification compliance review. It explicitly checks for feature completeness and prevents scope creep before assessing code maintainability.