cpm:review

Review epic and story documents with adversarial agent personas and severity scoring.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpm:review
Source: https://github.com/ninthspace/claude-code-marketplace/tree/main/cpm/skills/review
Command: npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial review of epic docs and stories helps teams surface gaps, risks, and misalignments early by challenging assumptions from multiple professional perspectives.

Core Features & Use Cases

  • Roster-driven critique: Loads a diverse agent roster and assigns reviewer roles to analyze artifacts.
  • Artifact-focused evaluation: Examines epic-level and story-level content, acceptance criteria, and dependencies to reveal gaps.
  • Remediation planning context: Produces structured findings with severity, references, and optional remediation steps for downstream planning.

Quick Start

Initiate a review session against an epic or story using the /cpm:review trigger to generate a findings report.

Frequently Asked Questions about cpm:review

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

FAQPage Schema
How do I perform an adversarial review of epic documentation?

Adversarial review of epic documentation loads the target artifact and applies multiple agent personas to identify gaps, risks, and assumption misalignments. It scores findings by severity and links them to specific stories and acceptance criteria.

What is the best way to surface hidden risks in story-level planning?

Surfacing hidden risks in story-level planning is done through roster-driven critique. Reviewer agents examine story content, acceptance criteria, and dependencies to reveal gaps and produce structured findings with severity scores.

Can I use library and ADR constraints to inform my documentation review?

Yes, you can use library and ADR constraints to inform your documentation review. The evaluation process leverages these constraints if present, applying them alongside assigned reviewer roles to examine artifacts and outline issues accurately.

How do I generate remediation tasks based on epic status?

To generate remediation tasks based on epic status, complete an artifact-focused evaluation first. The review process optionally produces standalone or remediation tasks derived from structured findings and the current epic status.

When do I need an adversarial review for my planning artifacts?

You need an adversarial review for your planning artifacts when you want to challenge assumptions from multiple professional perspectives early. This process helps teams surface misalignments, dependencies, and quality risks before downstream execution.