plan-check

Audit master plans and sub-plans for cohesion before coding.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Jennyfirrr/workspace-template --skill plan-check-jennyfirrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-check
Source: https://github.com/Jennyfirrr/workspace-template/tree/main/claude-skills/plan-check
Command: npx skills add https://github.com/Jennyfirrr/workspace-template --skill plan-check-jennyfirrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit a master plan and all its sub-plans to ensure cohesion before coding, preventing downstream conflicts where one plan undermines another.

Core Features & Use Cases

  • Verify readiness for each sub-plan and enforce a unified, cross-plan integration gate.
  • Validate the integration-matrix, dependency edges, and architectural invariants across plans.
  • Produce a single, actionable verdict (GREEN/YELLOW/RED) with per-plan findings and a consolidated risk assessment.

Quick Start

Run the /plan-check command to audit the most recently modified master plan under {{PLAN_DIR}} or specify a master path to audit a specific master plan.

Frequently Asked Questions about plan-check

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

FAQPage Schema
How do I check multi-plan dependencies before coding?▼

You can check multi-plan dependencies before coding by auditing the master plan and sub-plans to verify dependency ordering and integration matrix consistency. This ensures readiness and validates that no plan undermines another.

What is cross-plan cohesion and when do I need a readiness check?▼

Cross-plan cohesion is the alignment of a master plan with its sub-plans regarding dependencies, integration, and architecture. You need a readiness check during multi-plan cycles to prevent downstream conflicts where one plan undermines another.

How do I audit a master plan and its sub-plans for integration consistency?▼

You audit a master plan and its sub-plans for integration consistency by running a cross-plan check that evaluates per-sub-plan readiness, verifies the integration matrix, and detects file-touched drift. This produces a consolidated risk assessment with per-plan findings.

Can I verify sub-plan readiness and integration matrix consistency across multiple plans?▼

Yes, you can verify sub-plan readiness and integration matrix consistency across multiple plans by applying a cross-plan audit gate. This enforces per-sub-plan readiness, validates dependency edges, and produces a single actionable verdict for the entire cycle.

What is the best way to prevent downstream conflicts between a master plan and sub-plans?▼

The best way to prevent downstream conflicts between a master plan and sub-plans is to audit them for cohesion before coding. This verifies dependency ordering, checks file-touched drift, and enforces a unified integration gate to ensure architectural invariants hold.

Why does one sub-plan undermine another during multi-plan cycles?▼

One sub-plan undermines another during multi-plan cycles due to unverified dependency ordering and integration matrix inconsistencies. Auditing the master plan and sub-plans for cohesion before coding identifies these architectural conflicts and file-touched drift early.