creview

Review specification artifacts for assumptions, edge cases, and security gaps.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill creview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creview
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/creview
Command: npx skills add https://github.com/joshft/correctless --skill creview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product and software teams surface unstated assumptions, untested edge cases, and security gaps in specifications before implementation, reducing downstream defects and rework.

Core Features & Use Cases

  • Unstated Assumption Discovery: Identifies implicit assumptions in specs and artifacts (architecture, data flow, constraints).
  • Edge Case & Security Gap Analysis: Detects missing edge cases and potential security concerns across the spec lifecycle.
  • Structured Findings & Recommendations: Outputs concrete, actionable findings with proposed rewrites and risk dispositions (accept/reject/modify/defer) for integration into the workflow.
  • Progressive Review Workflow: Follows the defined multi-phase checklists (assumptions, testability, edge cases, antipatterns, integration tests, security, compliance, self-assessment).

Quick Start

Provide a complete spec review by enumerating gaps, then deliver a structured report with risk levels and rewrite suggestions.

Frequently Asked Questions about creview

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

FAQPage Schema
How do I find unstated assumptions and security gaps in a spec?

To identify unstated assumptions and security gaps in a spec, apply a phased review workflow covering testability, edge cases, antipatterns, and compliance to produce concrete risks and rewrite suggestions.

What is a structured spec review for risk management?

A structured spec review for risk management systematically examines artifacts to surface missing edge cases and implicit constraints, yielding actionable findings with explicit dispositions like accept, reject, or defer.

How do I enforce dispositions for edge cases found during spec review?

To enforce dispositions for edge cases found during spec review, demand explicit decisions—accept, reject, modify, or defer—for each finding and require concrete rewrites or new rules to address the identified gaps.

Can I check compliance and integration test coverage using a spec review workflow?

Yes, you can check compliance and integration test coverage by applying a multi-phase review checklist to the spec's artifacts, evaluating security and compliance rules to output structured risk levels and actionable recommendations.

Best way to surface missing testability and antipatterns in software specifications?

The best way to surface missing testability and antipatterns in software specifications is to run a skeptical, progress-visible review that evaluates artifacts phase-by-phase, proposing concrete rewrites for each discovered gap.