plan-check

Audit plan implementations by comparing planned and actual changes.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill plan-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-check
Source: https://github.com/skaisser/blueprint/tree/main/skills/plan-check
Command: npx skills add https://github.com/skaisser/blueprint --skill plan-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit implementations against the plan — compare planned vs actual changes, detect orphaned test references, fix checkbox mismatches, and sync frontmatter counts. It ensures the project artifacts reflect the intended plan and prevents drift between planning and execution.

Core Features & Use Cases

  • Compare planned changes with actual changes to surface drift between plan and implementation.
  • Detect orphaned test references and mismatched task markers to maintain traceability.
  • Sync frontmatter counts and metadata to ensure consistency across plan and PR checks.
  • Triggered by user phrases like "/plan-check", "plan audit", "verify implementation", and "did we implement everything" to act as a quality gate before PRs.

Quick Start

After plan approval, run /plan-check to audit the plan against the current implementation and surface any discrepancies.

Frequently Asked Questions about plan-check

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

FAQPage Schema
How do I audit implementation against a project plan?

To audit implementation against a project plan, compare planned changes with actual commits to surface drift. This detects orphaned test references and mismatched task markers to maintain traceability across the project.

What is the best way to verify implementation before creating a pull request?

To verify implementation before a pull request, run a plan audit to compare planned versus actual changes. This quality gate surfaces discrepancies, syncs frontmatter counts, and ensures the project artifacts reflect the intended plan.

How do I detect orphaned test references in my workflow?

To detect orphaned test references, compare your planned changes against the actual commits to identify mismatches. This traceability check flags test references that are no longer connected to the current implementation.

How do I sync frontmatter counts with actual task completion?

To sync frontmatter counts with task completion, audit the plan file against the current implementation. This updates the plan metadata and ensures checkbox consistency across plan and PR checks without changing the source code.

Can I compare planned changes with actual git commits without modifying source code?

Yes, you can compare planned changes with actual git commits without modifying source code. The audit process diffs commits and updates the plan metadata accordingly to reflect the true state of the implementation.