review

Route plan-design-RFC pre-flight checks and triage reviewer findings into integration or PM escalation.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill review-dbc-oduffy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/review
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill review-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns completed plan/design/RFC work into a structured review-to-integration workflow, so PMs can make clear scope/ship decisions while EMs and reviewers apply consistent technical and evidence checks.

Core Features & Use Cases

  • Outgoing plan pre-flight checks: Runs prior-art and external-API citation checks (plus lightweight acceptance-criteria shape and internal completeness offers) before the main reviewer reads the plan.
  • Reviewer routing and sequencing: Selects domain and/or generalist reviewers via routing fragments and enforces sequential integration (no parallelization for plan reviews).
  • Incoming findings triage: Applies a strict disposition table for findings, integrating tradeoff-free corrections automatically while escalating scope/architectural decisions to the PM.

Quick Start

Use coordinator:review when an EM has a plan/RFC ready for review or when review findings have landed on a plan and need to be processed into PM decisions and integrations.

Frequently Asked Questions about review

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

FAQPage Schema
How do I route plan review findings into PM decisions and integrations?

Plan review findings are routed using a strict triage policy that automatically integrates tradeoff-free corrections while escalating scope and build-vs-defer decisions to the PM.

What are plan pre-flight checks and how do they work for RFC reviews?

Pre-flight checks run prior-art and external-API citation validation, plus lightweight acceptance-criteria shape checks, before the main reviewer reads the RFC or plan to ensure readiness.

Can I run parallel pre-flight checks and parallel reviewer integration for plan reviews?

You can run parallel pre-flight checks where specified, but reviewer integration is strictly sequential and deterministic, meaning no parallelization is allowed for plan reviews.

How are reviewers selected for architectural plan and RFC reviews?

Reviewers are selected via routing-table based fragments that assign domain or generalist reviewers, enforcing deterministic sequencing to process architectural review findings.

Does this handle evidence-driven disagreements and tradeoff signals in RFC reviews?

RFC reviews apply a strict disposition table that processes evidence-driven disagreements and tradeoff signals, integrating corrections while escalating architectural decisions.

When do I need prior-art checking and acceptance-criteria readiness for product reviews?

Prior-art checking and acceptance-criteria readiness are needed when a completed plan or RFC enters the review-to-integration workflow to ensure PMs can make clear scope decisions.