review

Review existing plan artifacts and return an APPROVED, REVISE, or REJECT verdict.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lpjhelder/kronon-forge --skill review-lpjhelder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/review
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill review-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewer-only pass for planning reviews ensures separation between authoring and verdicts, and streamlines artifact quality checks.

Core Features & Use Cases

  • Enforced evaluation: Triggers a separate Critic-based review of existing plans via the Plan skill in review mode.
  • Artifact quality gate: Verifies that cleanup or refactor work is accompanied by a plan, regression tests, or explicit test gaps.
  • Use Case: A product team uses the Review skill to independently validate a plan before execution, reducing risk and improving governance.

Quick Start

Run the Plan skill in review mode against the target plan to generate a verdict.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform an independent plan review for existing workflow artifacts?

A reviewer-only pass evaluates existing plan artifacts using a Critic to ensure separation between authoring and verdicts, returning an APPROVED, REVISE, or REJECT verdict with concrete feedback.

How do I verify plan artifacts have adequate regression tests before execution?

To verify regression tests, the skill acts as an artifact quality gate, checking that cleanup or refactor work is accompanied by a plan, regression tests, or explicit test gaps before execution.

What is a reviewer-only pass in governance and planning workflows?

A reviewer-only pass in governance is an enforced evaluation that separates plan authoring from verdicts, independently validating artifacts to reduce execution risk and improve quality checks.

Does this plan review skill work with artifacts stored in specific directories?

Yes, the skill applies to plan artifacts stored in .forge/plans or any specified file paths, reading the artifacts to evaluate them and generate a concrete critique verdict.

What verdicts can I expect when evaluating a plan artifact?

When evaluating a plan artifact, you can expect an APPROVED, REVISE, or REJECT verdict, accompanied by concrete feedback detailing any required cleanup or missing regression tests.

When should I use a separate critic evaluation instead of standard plan authoring?

You should use a separate critic evaluation when independent governance is required to validate a plan before execution, ensuring artifact quality without bias from the authoring process.