메뉴
"Use when checking Plan Enforcer progress --- shows scoreboard, current task, unverified items, and stale warnings from the active ledger"
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | plan-enforcer-status |
| description | Use when checking Plan Enforcer progress --- shows scoreboard, current task, unverified items, and stale warnings from the active ledger |
Read .plan-enforcer/ledger.md. If missing: "No active Plan Enforcer session. Activate with /plan-enforcer <plan-file>"
If the installed CLI is available, prefer running node ~/.claude/skills/plan-enforcer/src/status-cli.js .plan-enforcer/ledger.md so the output matches the shared formatter exactly.
Parse the Task Ledger table. Count rows by status column:
| Metric | Source |
|---|---|
| done | status = done OR verified |
| verified | status = verified |
| skipped | status = skipped OR superseded |
| blocked | status = blocked |
| total | all rows |
| drift | count of Decision Log entries tagged drift/unplanned |
| current | first row where status = in-progress OR pending |
---🛡️Plan Enforcer Status ------------------------------
{done}/{total} tasks | {verified} verified | {skipped} skipped | {blocked} blocked
Tier: {tier} | Drift: {drift} | Current: T{N}
---------------------------------------------------------
Current Task: T{N} --- {task description}
Unverified (done but no evidence):
T3 --- Add session storage
T6 --- Configure CORS
Blocked:
T4 --- Write integration tests (DB fixtures unavailable)
---------------------------------------------------------
Omit sections with zero items. At advisory tier (no ledger file), generate from conversation context and note the output is from memory, not file.
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"