rpi-plan-critique

Installation
SKILL.md

RPI Plan Critique

Goal

Return a substantive, evidence-grounded credibility assessment of an RPI plan and its phase details. The critique is read-only with respect to plan sources and writes only the caller-specified critique artifact.

Flow

  1. Confirm the exact plan, phase-details, evidence, requirements, decisions, dependencies, acceptance criteria, and critique output path supplied by the caller.
  2. Read the supplied materials. Do not perform open-ended research or infer missing evidence as fact.
  3. Define the supplied inputs and criterion boundary, then assess the full boundary once across requirements, research, phases, tasks, acceptance criteria, dependencies, decisions, risks, and missed concerns. Return every actionable concern available from the supplied evidence in one complete finding set rather than serializing discoverable findings across critique passes.
  4. Write the critique using templates/plan-critique.md. Use severity-graded PC-xxx findings keyed to relevant requirement, research, phase, or task IDs. For each actionable finding, name the smallest useful change, action owner, exact resolving evidence, and whether it is a direct planner correction or needs a significant or divergent user decision.
  5. Record critique execution as Complete, Partial, or Blocked, separately from the Pass, Revise, or Blocked verdict. A passing critique may identify residual risks that the planning parent has explicitly accepted.

Inputs

Installs
2
GitHub Stars
1.3K
First Seen
5 days ago
rpi-plan-critique — microsoft/hve-core