agentic-review-work

Audit a codebase against a plan document and produce a PASS/FAIL review.

3|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/alphabeen/oh-my-jinho --skill agentic-review-work-alphabeen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-review-work
Source: https://github.com/alphabeen/oh-my-jinho/tree/main/skills/agentic-review-work
Command: npx skills add https://github.com/alphabeen/oh-my-jinho --skill agentic-review-work-alphabeen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independently verifies implementation results by reading only the plan document and inspecting the codebase from scratch to ensure alignment with the planned goals without relying on execution context.

Core Features & Use Cases

  • Plan-driven verification: reads the plan, audits the codebase against plan requirements, runs tests, and produces a PASS/FAIL verdict.
  • Execution isolation: operates without pulling in runtime logs, worker outputs, or task completion summaries.
  • Documentation generation: saves a formal review document detailing findings and verdict.

Quick Start

Provide the plan file path to the verification workflow to generate a structured PASS/FAIL review document

Frequently Asked Questions about agentic-review-work

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

FAQPage Schema
How do I verify codebase changes against a plan document without execution context?

Verify codebase changes against a plan document by loading the plan file, inspecting the codebase from scratch, running specified tests, and checking Git history to produce a formal PASS or FAIL review.

What is plan-driven codebase verification and how does it work?

Plan-driven codebase verification reads a plan file path and audits the implementation independently. It inspects the codebase against plan requirements, runs tests, validates Git history, and saves a structured review document with a PASS or FAIL verdict.

How do I generate a PASS or FAIL review document after executing a development plan?

Generate a PASS or FAIL review document by providing the plan file path to the verification workflow. The system audits the codebase, executes plan-specified tests, validates Git history, and outputs a structured review detailing findings.

Does plan-driven verification require runtime logs or worker task completion summaries?

Plan-driven verification operates in execution isolation and does not require runtime logs, worker outputs, or task completion summaries. It independently audits the codebase and runs tests based solely on the plan document.

Can I use this verification approach for post-plan execution scenarios requiring formal validation?

Yes, plan-driven verification is designed for post-plan execution scenarios requiring formal validation. It enforces loading the plan file, inspecting the codebase, performing test execution, validating Git history, and saving a structured review document.

What is the best way to independently audit implementation results against planned goals?

The best way to independently audit implementation results is reading only the plan document and inspecting the codebase from scratch. This ensures alignment with planned goals without relying on execution context or runtime outputs.