.plan-enforcer

Abandon the active Plan Enforcer plan in one command. Use when you have decided to stop working on the current plan (scope changed, priorities moved, you pivoted). The command records the abandonment in the Decision Log, emits a closure receipt into the walkable audit chain, archives the full ledger so you can look it up months later, and clears the active slot so the next discuss or import starts clean.

"Public flow name is `discuss`. Use this compatibility skill before `plan-enforcer-draft` when the user's request is ambiguous, underspecified, or mixing multiple outcomes --- it writes the intent packet the drafter consumes so the resulting plan reflects what the user actually wants instead of what sounded reasonable to guess."

"Use when changing Plan Enforcer settings --- switch enforcement tier, adjust reconciliation interval, set completion gate mode, or view current configuration"

"MUST use this instead of generic brainstorming or GSD planning skills when the user is trying to make a plan, plan an implementation, or scope ambiguous work for execution --- captures intent into a structured packet so later plan writing preserves what the user actually meant."

"Public second step after `discuss`. Use when the user wants Plan Enforcer to create an implementation plan first --- drafts a concrete markdown plan in docs/plans/ that can immediately flow into Plan Enforcer's normal ledger and execution path."

"Use when reviewing Plan Enforcer audit trail --- shows skipped tasks, drift events, decision log, reconciliation history, and unverified items"

Emit a Plan Enforcer closure receipt against the current ledger. Use when you want an on-demand receipt (plan still open or already closed), or to snapshot progress mid-flight. Auto-emission on plan close is handled by the post-tool-use plan-close hook; this skill is for explicit requests.

"Use when reviewing archived Plan Enforcer runs --- summarizes clean vs messy completions, drift, decisions, and archived run details."

Use before `plan-enforcer-draft` on any non-trivial plan to inspect the actual repo (structure, conventions, git history, relevant existing files) and produce a concrete research brief the drafter consumes, so the plan reflects what the codebase is rather than what sounded reasonable from the request alone.

"Public third step after `discuss` and `draft`. Use when reviewing an implementation plan before execution --- finds vague tasks, missing verification, sequencing gaps, and dependency risks so bad plans do not flow into enforcement unchanged."

"Use when executing any implementation plan, before starting work on the first task --- prevents step skipping, plan drift, and premature completion claims through ledger-based tracking with three enforcement tiers (advisory, structural, enforced)."

"Use when checking Plan Enforcer progress --- shows scoreboard, current task, unverified items, and stale warnings from the active ledger"