rpi-plan-critique

Critiques RPI plans and phase details against supplied evidence with severity-graded findings.

1.4k|284|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/microsoft/hve-core --skill rpi-plan-critique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpi-plan-critique
Source: https://github.com/microsoft/hve-core/tree/main/.github/skills/rpi/rpi-plan-critique
Command: npx skills add https://github.com/microsoft/hve-core --skill rpi-plan-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning documents often contain gaps, unsupported assumptions, or missing evidence that only surface during implementation. This Skill performs an independent, read-only credibility assessment of an RPI plan and its phase details so weaknesses are caught before execution begins.

Core Features & Use Cases

  • Evidence-grounded critique: Assesses requirements, research, phases, tasks, dependencies, decisions, and acceptance criteria strictly against caller-supplied evidence, without open-ended research.
  • Severity-graded findings: Produces PC-xxx findings with related IDs, impact, smallest useful change, action owner, and decision routing (direct planner correction vs. user decision).
  • Structured verdicts: Returns a Pass, Revise, or Blocked verdict alongside a Complete, Partial, or Blocked execution status, using a standardized critique template.
  • Use Case: After drafting an implementation plan with the rpi-plan stage, dispatch this critique to verify the plan is credible for implementation and receive one complete set of actionable findings before proceeding.

Quick Start

Critique the plan at .copilot-tracking/plans/2026-08-13/my-task-plan.md and its phase details against the supplied research evidence, writing the critique to the specified output path.

Frequently Asked Questions about rpi-plan-critique

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

FAQPage Schema
How do I critique an RPI plan before implementation?

Invoke the rpi-plan-critique skill with the plan path, phase-details path, evidence pointers, and an output path. It reads the supplied materials and writes a severity-graded critique with a Pass, Revise, or Blocked verdict.

What inputs does the plan critique require?

It requires the plan and phase-details paths, caller requirements and task context, supplied research and evidence pointers, decisions, dependencies, acceptance criteria, and one critique output path. It does not perform research beyond the supplied inputs.

Does the critique modify the plan or phase details?

No. The critique is strictly read-only with respect to plan sources, phase details, research, and review records. It writes only the caller-specified critique artifact and returns findings for the planning parent to act on.

What do Pass, Revise, and Blocked verdicts mean?

Pass means the plan is credible for implementation with any residual risks explicitly accepted. Revise means substantive findings require a plan change. Blocked means the supplied evidence cannot support a decision-critical assessment.

When should a plan critique not be used?

Do not use it to grade formatting, document cosmetics, or template adherence, since it only reports substantive planning risks. It also cannot fill evidence gaps itself; material research gaps are routed back as Blocked or Revise findings.