plan-conformance-execution

Executes authorized implementation plans while verifying repository state and conformance.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill plan-conformance-execution-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-conformance-execution
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/plan-conformance-execution
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill plan-conformance-execution-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running software implementation work often drifts from its approved plan: repository state changes silently, steps get marked done without evidence, and deviations are absorbed without record. This Skill enforces a disciplined execution loop that keeps the plan, repository state, and validation evidence continuously reconciled. ## Core Features & Use Cases - State Rehydration & Drift Detection: On every session, re-reads the plan, checkpoints, and handoff snapshot, then compares them against actual Git state to classify drift as compatible, plan-relevant, or unknown. - Explicit Conformance Classification: Every change is classified as CONFORMING, LOCAL_VARIATION, PLAN_GAP, DEVIATION_REQUIRED, PLAN_INVALID, BLOCKED, or OUT_OF_SCOPE, preventing silent redesign and scope creep. - Checkpoint & Handoff Lifecycle: Creates sequential checkpoints with validation evidence, maintains a compliance matrix, and produces resumable handoff snapshots so another agent can continue without conversational memory. - Use Case: A team maintains a multi-milestone refactoring plan under docs/public/plans/active/. An agent executing it across several sessions uses this Skill to resume safely after interruptions, prove each step with test evidence, and archive the plan when complete. ## Quick Start Execute the active plan in docs/public/plans/active/ and continue from its latest checkpoint, verifying repository state before making any changes.

Frequently Asked Questions about plan-conformance-execution

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

FAQPage Schema
How do I resume a paused implementation plan in a new session?

Read the full plan, the Handoff Snapshot, and the latest checkpoint, then inspect the actual repository state and compare it against recorded state. Reconcile any drift and revalidate if needed before continuing; never trust the snapshot blindly.

How do I prevent scope creep during long-running implementation work?

Map every material change to the active plan step, a prerequisite, or planned validation. Classify anything unplanned through the conformance decision procedure, and treat changes with no defensible mapping as out of scope.

When should this skill be activated?

Only when the user explicitly asks to execute, implement, apply, or continue a plan, and that plan resolves to a non-terminal active plan under docs/public/plans/active/. Ordinary complex tasks without explicit plan authorization should not trigger it.

What happens when repository state diverges from the plan?

The state is marked DIVERGED and substantial new implementation stops. The drift is investigated and classified as compatible, plan-relevant, or unknown, then reconciled with a new checkpoint before execution continues.

When is a plan step considered complete?

A step is DONE only when intended behavior exists, invariants hold, targeted validation passes, the diff conforms to scope, and completion evidence is recorded. Writing code alone never marks a step complete.

What are the limitations of plan-conformance execution?

It requires an existing authorized plan and will not author one automatically. It also cannot proceed safely when state is BLOCKED or DIVERGED, and material plan changes require explicit replanning rather than silent redesign.