@sienklogic/plan-build-run 2.0.0 → 2.0.1

package/plugins/pbr/skills/health/SKILL.md

@@ -1,186 +1,221 @@
----
-name: health
-description: "Check planning directory integrity. Find and fix corrupted state."
-allowed-tools: Read, Bash, Glob, Grep
----
-
-# /pbr:health — Planning Directory Diagnostics
-
-You are running the **health** skill. Your job is to validate the integrity of the `.planning/` directory, report problems, and suggest targeted fixes. You never auto-repair anything.
-
-This skill runs **inline** and is **read-only** — it never modifies any files.
-
----
-
-## How Checks Work
-
-Each check follows the common pattern. Read `skills/health/templates/check-pattern.md.tmpl` for the shared execution flow: target files, validate against rules, classify as PASS/FAIL/WARN/INFO, and record the result with a fix suggestion for any failures.
-
-Read `skills/health/templates/output-format.md.tmpl` for the output format: summary table, status indicators, issues list, optional recent decisions, and final result line.
-
----
-
-## Checks
-
-Run all 9 checks in order. Collect results and present them together at the end.
-
-### Check 1: Structure
-
-Validate `.planning/` exists with required scaffolding: `STATE.md`, `config.json`, `ROADMAP.md`.
-
-- If `.planning/` is missing: FAIL the entire health check immediately. Display:
-```
-╔══════════════════════════════════════════════════════════════╗
-║  ERROR                                                       ║
-╚══════════════════════════════════════════════════════════════╝
-
-No .planning/ directory found.
-
-**To fix:** Run `/pbr:begin` to initialize.
-```
-Stop all further checks.
-- PASS: All three required files exist
-- FAIL: List each missing file — "Run `/pbr:begin` to re-initialize, or create the file manually."
-
-### Check 2: Config Validity
-
-Parse `.planning/config.json` as JSON. Check required fields: `projectName`, `version`. Check recommended fields: `phases`, `currentPhase`.
-
-- PASS: Valid JSON with all required fields
-- FAIL (parse error): Report the parse error message — "Open the file and correct the syntax."
-- FAIL (missing required field): Report which field — "Add the field to config.json."
-- WARN (missing recommended field): Report which field — "This may cause issues with some skills."
-
-### Check 3: Phase Consistency
-
-Compare directories in `.planning/phases/` against phases defined in `ROADMAP.md`.
-
-- PASS: Every directory matches a ROADMAP.md phase; no started phases are missing directories
-- FAIL (orphan directory): Directory exists but not in ROADMAP.md — "Add to ROADMAP.md or remove the directory."
-- FAIL (missing directory): ROADMAP.md lists phase as in-progress but directory missing — "Create the directory or update ROADMAP.md."
-- Note: Future phases without directories are normal (not a failure).
-
-### Check 4: Plan/Summary Pairing
-
-Glob all `PLAN*.md` and `SUMMARY*.md` in `.planning/phases/`. Match by plan number. A PLAN without SUMMARY is normal unless the phase is marked complete.
-
-- PASS: All pairings valid, no orphaned summaries
-- FAIL (orphaned summary): SUMMARY has no matching PLAN — "Verify and remove or re-pair."
-- WARN (missing summary in complete phase): Phase marked complete but plan has no SUMMARY — "Execute with `/pbr:build` or mark phase incomplete."
-
-### Check 5: STATE.md Accuracy
-
-Extract current phase, plan identifier, and progress percentage from `STATE.md`. Verify each against the file system.
-
-- PASS: All STATE.md references match the file system
-- FAIL (stale phase): Referenced phase directory does not exist — "Update STATE.md to reflect the actual current phase."
-- FAIL (stale plan): Referenced plan file does not exist — "Update STATE.md to the correct current plan."
-- FAIL (wrong progress): Stated progress does not match actual plan/summary counts — "Update the progress in STATE.md."
-- WARN (no position): No current phase or plan specified — "Fine for new projects but may indicate lost state."
-
-### Check 6: Frontmatter Validity
-
-Glob all `PLAN*.md` and `SUMMARY*.md` in `.planning/phases/`. Each file must start with `---`, have a closing `---`, contain valid YAML, and include required fields: `title`, `status`.
-
-- PASS: All files have valid frontmatter with required fields
-- FAIL (no frontmatter): "Add frontmatter block starting with `---` at the top of the file."
-- FAIL (malformed): Report the YAML error — "Correct the YAML syntax between the `---` delimiters."
-- FAIL (missing field): Report which field — "Add `{field}: {suggested value}` to the frontmatter."
-
-### Check 7: ROADMAP/STATE Sync
-
-Compare ROADMAP.md phase statuses against STATE.md current position. Flag if ROADMAP says a phase is "verified" but STATE says it is "building", or if phases after current are marked complete.
-
-- PASS: ROADMAP and STATE are consistent
-- FAIL (mismatch): Report both statuses — "Update STATE.md to match ROADMAP.md, or vice versa."
-- WARN (drift): Current phase in STATE.md is behind phases marked complete in ROADMAP.md.
-
-### Check 8: Hook Execution Log
-
-Check if `.planning/logs/hooks.jsonl` exists. If so, scan last 20 entries for `result: "error"` or `result: "unlink-failed"`.
-
-- PASS: Log exists with no recent errors
-- WARN (errors found): Report error count and most recent error description — "Hooks may not be firing correctly."
-- INFO (no log): "No hook log found. Normal if no hooks have fired yet."
-
-### Check 9: Config Completeness
-
-Read `.planning/config.json` and check for fields referenced by skills:
-- `features.auto_continue` (build skill, auto-continue.js hook)
-- `features.team_discussions` (config skill)
-- `features.goal_verification` (build, review skills)
-- `features.integration_verification` (review skill)
-- `git.mode` (config skill)
-
-- PASS: All expected fields present
-- WARN (missing fields): Report each missing field and which skill uses it — "Run `/pbr:config` to set all options."
-
----
-
-## Bonus: Recent Decisions
-
-After all checks, look for `.planning/logs/decisions.jsonl`. If it exists, display the last 5 entries as `- {date}: {summary} (phase {N})`. If it does not exist, skip silently.
-
----
-
-## Completion
-
-After all checks complete, display the branded result:
-
-**If all checks passed (0 failures):**
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► HEALTH CHECK PASSED ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-{N} checks passed, {M} warnings
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Continue your workflow** — planning directory is healthy
-
-`/pbr:status`
-
-<sub>`/clear` first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- `/pbr:continue` — execute next logical step
-- `/pbr:config` — adjust settings
-
-───────────────────────────────────────────────────────────────
-```
-
-**If failures found:**
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► HEALTH CHECK FAILED ⚠
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-{N} checks passed, {F} failures, {M} warnings
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Fix the failures** listed above, then re-run
-
-`/pbr:health`
-
-───────────────────────────────────────────────────────────────
-```
-
----
-
-## Anti-Patterns
-
-1. **DO NOT** modify any files — this is strictly read-only
-2. **DO NOT** auto-repair anything — present fixes and let the user decide
-3. **DO NOT** skip checks that depend on missing files — report the dependency failure and continue
-4. **DO NOT** treat warnings as failures in the summary count — only count FAIL items
-5. **DO NOT** read full plan/summary contents — frontmatter and existence checks are sufficient
-6. **DO NOT** fail silently — every check must produce an explicit PASS, WARN, or FAIL
-7. **DO NOT** suggest running destructive commands — fixes should be safe, targeted edits
+---
+name: health
+description: "Check planning directory integrity. Find and fix corrupted state."
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+**STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 tokens. Begin executing Step 1 immediately.**
+
+## Step 0 — Immediate Output
+
+**Before ANY tool calls**, display this banner:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PLAN-BUILD-RUN ► HEALTH CHECK
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+Then proceed to Step 1.
+
+# /pbr:health — Planning Directory Diagnostics
+
+You are running the **health** skill. Your job is to validate the integrity of the `.planning/` directory, report problems, and suggest targeted fixes. You never auto-repair anything.
+
+This skill runs **inline** and is **read-only** — it never modifies any files.
+
+---
+
+## How Checks Work
+
+Each check follows the common pattern. Read `skills/health/templates/check-pattern.md.tmpl` for the shared execution flow: target files, validate against rules, classify as PASS/FAIL/WARN/INFO, and record the result with a fix suggestion for any failures.
+
+Read `skills/health/templates/output-format.md.tmpl` for the output format: summary table, status indicators, issues list, optional recent decisions, and final result line.
+
+---
+
+## Checks
+
+Run all 10 checks in order. Collect results and present them together at the end.
+
+### Check 1: Structure
+
+Validate `.planning/` exists with required scaffolding: `STATE.md`, `config.json`, `ROADMAP.md`.
+
+- If `.planning/` is missing: FAIL the entire health check immediately. Display:
+```
+╔══════════════════════════════════════════════════════════════╗
+║  ERROR                                                       ║
+╚══════════════════════════════════════════════════════════════╝
+
+No .planning/ directory found.
+
+**To fix:** Run `/pbr:begin` to initialize.
+```
+Stop all further checks.
+- PASS: All three required files exist
+- FAIL: List each missing file — "Run `/pbr:begin` to re-initialize, or create the file manually."
+
+### Check 2: Config Validity
+
+Parse `.planning/config.json` as JSON. Check required fields: `version`, `depth`. Check recommended fields: `features`, `models`.
+
+- PASS: Valid JSON with all required fields
+- FAIL (parse error): Report the parse error message — "Open the file and correct the syntax."
+- FAIL (missing required field): Report which field — "Add the field to config.json."
+- WARN (missing recommended field): Report which field — "This may cause issues with some skills."
+
+### Check 3: Phase Consistency
+
+Compare directories in `.planning/phases/` against phases defined in `ROADMAP.md`.
+
+- PASS: Every directory matches a ROADMAP.md phase; no started phases are missing directories
+- FAIL (orphan directory): Directory exists but not in ROADMAP.md — "Add to ROADMAP.md or remove the directory."
+- FAIL (missing directory): ROADMAP.md lists phase as in-progress but directory missing — "Create the directory or update ROADMAP.md."
+- Note: Future phases without directories are normal (not a failure).
+
+### Check 4: Plan/Summary Pairing
+
+Glob all `PLAN*.md` and `SUMMARY*.md` in `.planning/phases/`. Match by plan number. A PLAN without SUMMARY is normal unless the phase is marked complete.
+
+- PASS: All pairings valid, no orphaned summaries
+- FAIL (orphaned summary): SUMMARY has no matching PLAN — "Verify and remove or re-pair."
+- WARN (missing summary in complete phase): Phase marked complete but plan has no SUMMARY — "Execute with `/pbr:build` or mark phase incomplete."
+
+### Check 5: STATE.md Accuracy
+
+Extract current phase, plan identifier, and progress percentage from `STATE.md`. Verify each against the file system.
+
+- PASS: All STATE.md references match the file system
+- FAIL (stale phase): Referenced phase directory does not exist — "Update STATE.md to reflect the actual current phase."
+- FAIL (stale plan): Referenced plan file does not exist — "Update STATE.md to the correct current plan."
+- FAIL (wrong progress): Stated progress does not match actual plan/summary counts — "Update the progress in STATE.md."
+- WARN (no position): No current phase or plan specified — "Fine for new projects but may indicate lost state."
+
+### Check 6: Frontmatter Validity
+
+Glob all `PLAN*.md` and `SUMMARY*.md` in `.planning/phases/`. Each file must start with `---`, have a closing `---`, contain valid YAML, and include required fields: `title`, `status`.
+
+- PASS: All files have valid frontmatter with required fields
+- FAIL (no frontmatter): "Add frontmatter block starting with `---` at the top of the file."
+- FAIL (malformed): Report the YAML error — "Correct the YAML syntax between the `---` delimiters."
+- FAIL (missing field): Report which field — "Add `{field}: {suggested value}` to the frontmatter."
+
+### Check 7: ROADMAP/STATE Sync
+
+Compare ROADMAP.md phase statuses against STATE.md current position. Flag if ROADMAP says a phase is "verified" but STATE says it is "building", or if phases after current are marked complete.
+
+- PASS: ROADMAP and STATE are consistent
+- FAIL (mismatch): Report both statuses — "Update STATE.md to match ROADMAP.md, or vice versa."
+- WARN (drift): Current phase in STATE.md is behind phases marked complete in ROADMAP.md.
+
+### Check 8: Hook Execution Log
+
+Check if `.planning/logs/hooks.jsonl` exists. Also check the legacy path `.planning/.hook-log` (the logger migrates this automatically, but it may still exist if hooks haven't fired since the migration was added). Use whichever file exists (prefer `hooks.jsonl`). If found, scan last 20 entries for `decision: "error"` or `decision: "unlink-failed"`.
+
+- PASS: Log exists with no recent errors
+- WARN (errors found): Report error count and most recent error description — "Hooks may not be firing correctly."
+- INFO (no log): "No hook log found. Normal if no hooks have fired yet."
+
+### Check 9: Config Completeness
+
+Read `.planning/config.json` and check for fields referenced by skills:
+- `features.auto_continue` (build skill, auto-continue.js hook)
+- `features.team_discussions` (config skill)
+- `features.goal_verification` (build, review skills)
+- `features.integration_verification` (review skill)
+- `git.mode` (config skill)
+- `planning.commit_docs` (import, discuss, quick skills) — must be a boolean; validate that the value is strictly `true` or `false`, not a string or number
+
+- PASS: All expected fields present with correct types
+- WARN (missing fields): Report each missing field and which skill uses it — "Run `/pbr:config` to set all options."
+
+### Check 10: Orphaned Crash Recovery Files
+
+The executor creates `.PROGRESS-{plan_id}` files as crash recovery breadcrumbs during builds and deletes them after `SUMMARY.md` is written. Similarly, `.checkpoint-manifest.json` files track checkpoint state during execution. If the executor crashes mid-build, these files remain and could confuse future runs.
+
+Glob for `.planning/phases/**/.PROGRESS-*` and `.planning/phases/**/.checkpoint-manifest.json`.
+
+- PASS: No orphaned files found
+- WARN (orphaned progress files): List each file with its parent phase directory:
+  ```
+  Orphaned progress files detected:
+  - .planning/phases/02-auth/.PROGRESS-02-01 (executor may have crashed)
+  ```
+  Fix suggestion: "These are crash recovery breadcrumbs from interrupted builds. Safe to delete if no `/pbr:build` is currently running. Remove with `rm <path>`."
+- WARN (orphaned checkpoint manifests): List each file:
+  ```
+  Orphaned checkpoint manifests detected:
+  - .planning/phases/02-auth/.checkpoint-manifest.json (stale build checkpoint)
+  ```
+  Fix suggestion: "Checkpoint manifests are leftover from interrupted builds. Safe to delete if no `/pbr:build` is currently running. Remove with `rm <path>`."
+
+---
+
+## Bonus: Recent Decisions
+
+After all checks, look for `.planning/logs/decisions.jsonl`. If it exists, display the last 5 entries as `- {date}: {summary} (phase {N})`. If it does not exist, skip silently.
+
+---
+
+## Completion
+
+After all checks complete, display the branded result:
+
+**If all checks passed (0 failures):**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PLAN-BUILD-RUN ► HEALTH CHECK PASSED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+{N} checks passed, {M} warnings
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Continue your workflow** — planning directory is healthy
+
+`/pbr:status`
+
+<sub>`/clear` first → fresh context window</sub>
+
+───────────────────────────────────────────────────────────────
+
+**Also available:**
+- `/pbr:continue` — execute next logical step
+- `/pbr:config` — adjust settings
+
+───────────────────────────────────────────────────────────────
+```
+
+**If failures found:**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PLAN-BUILD-RUN ► HEALTH CHECK FAILED ⚠
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+{N} checks passed, {F} failures, {M} warnings
+
+───────────────────────────────────────────────────────────────
+
+## ▶ Next Up
+
+**Fix the failures** listed above, then re-run
+
+`/pbr:health`
+
+───────────────────────────────────────────────────────────────
+```
+
+---
+
+## Anti-Patterns
+
+1. **DO NOT** modify any files — this is strictly read-only
+2. **DO NOT** auto-repair anything — present fixes and let the user decide
+3. **DO NOT** skip checks that depend on missing files — report the dependency failure and continue
+4. **DO NOT** treat warnings as failures in the summary count — only count FAIL items
+5. **DO NOT** read full plan/summary contents — frontmatter and existence checks are sufficient
+6. **DO NOT** fail silently — every check must produce an explicit PASS, WARN, or FAIL
+7. **DO NOT** suggest running destructive commands — fixes should be safe, targeted edits

package/plugins/pbr/skills/health/templates/check-pattern.md.tmpl

@@ -1,30 +1,30 @@
-# Health Check Execution Pattern
-
-Each of the 9 checks follows this common pattern. The check-specific details (what to read, what to validate, what constitutes PASS/FAIL) are defined in SKILL.md — this template describes only the shared execution flow.
-
-## Pattern
-
-```
-For check {check_number} ({check_name}):
-
-1. READ — Read the target file(s): {target_files}
-2. VALIDATE — Apply the check-specific rules: {validation_rules}
-3. CLASSIFY — Determine result:
-   - PASS: Validation succeeded, no issues found
-   - FAIL: A required condition is violated (counts toward issue total)
-   - WARN: A recommended condition is violated (does NOT count toward issue total)
-   - INFO: Informational note, not a problem
-4. RECORD — Store the result with:
-   - Status: [PASS], [FAIL], [WARN], or [INFO]
-   - Check name (short label)
-   - One-line summary of finding
-   - For FAIL/WARN: the specific file, the problem, and a concrete fix suggestion
-```
-
-## Rules
-
-- Every check MUST produce exactly one status line (PASS, FAIL, WARN, or INFO)
-- FAIL results MUST include: file path, problem description, and fix suggestion
-- Multiple failures within a single check produce multiple entries in the "Issues Found" section
-- Checks never auto-repair — they report only
-- If a check depends on a prior check's file (e.g., Check 2 needs config.json which Check 1 validates exists), and that file is missing, report the dependency failure and move on
+# Health Check Execution Pattern
+
+Each of the 9 checks follows this common pattern. The check-specific details (what to read, what to validate, what constitutes PASS/FAIL) are defined in SKILL.md — this template describes only the shared execution flow.
+
+## Pattern
+
+```
+For check {check_number} ({check_name}):
+
+1. READ — Read the target file(s): {target_files}
+2. VALIDATE — Apply the check-specific rules: {validation_rules}
+3. CLASSIFY — Determine result:
+   - PASS: Validation succeeded, no issues found
+   - FAIL: A required condition is violated (counts toward issue total)
+   - WARN: A recommended condition is violated (does NOT count toward issue total)
+   - INFO: Informational note, not a problem
+4. RECORD — Store the result with:
+   - Status: [PASS], [FAIL], [WARN], or [INFO]
+   - Check name (short label)
+   - One-line summary of finding
+   - For FAIL/WARN: the specific file, the problem, and a concrete fix suggestion
+```
+
+## Rules
+
+- Every check MUST produce exactly one status line (PASS, FAIL, WARN, or INFO)
+- FAIL results MUST include: file path, problem description, and fix suggestion
+- Multiple failures within a single check produce multiple entries in the "Issues Found" section
+- Checks never auto-repair — they report only
+- If a check depends on a prior check's file (e.g., Check 2 needs config.json which Check 1 validates exists), and that file is missing, report the dependency failure and move on

package/plugins/pbr/skills/health/templates/output-format.md.tmpl

@@ -1,63 +1,63 @@
-# Health Check Output Format
-
-Present results as a single report after all checks complete.
-
-## Summary Table
-
-```
-Planning Health Check
-=====================
-
-[PASS]  Structure           .planning/ exists, all required files present
-[FAIL]  Config              config.json missing required field `projectName`
-[PASS]  Phase consistency   Directories match ROADMAP.md phases
-[PASS]  Plan/Summary        All pairings valid
-[FAIL]  STATE.md accuracy   Phase reference is stale
-[PASS]  Frontmatter         All PLAN/SUMMARY files have valid frontmatter
-[PASS]  ROADMAP/STATE sync  ROADMAP and STATE phase statuses are consistent
-[PASS]  Hook log            No recent hook errors
-[PASS]  Config completeness All expected fields present
-```
-
-## Status Indicators
-
-| Indicator | Meaning | Counts as Issue? |
-|-----------|---------|-----------------|
-| `[PASS]`  | Check passed, no problems | No |
-| `[FAIL]`  | Required condition violated | **Yes** |
-| `[WARN]`  | Recommended condition violated | No |
-| `[INFO]`  | Informational note | No |
-
-## Issues Section
-
-Only shown when at least one FAIL exists:
-
-```
-Issues Found: {count}
----------------
-
-1. {problem description}
-   File: {file path}
-   Fix:  {concrete fix suggestion}
-
-2. {problem description}
-   File: {file path}
-   Fix:  {concrete fix suggestion}
-```
-
-## Recent Decisions (Bonus)
-
-If `.planning/logs/decisions.jsonl` exists, show the last 5 entries:
-
-```
-Recent Decisions:
-- {date}: {summary} (phase {N})
-- {date}: {summary} (phase {N})
-```
-
-If the file does not exist, skip silently.
-
-## Final Line
-
-- With issues: `Result: {N} issues found. Review and apply fixes manually.`
-- All passed: `Result: All checks passed. Planning directory is healthy.`
+# Health Check Output Format
+
+Present results as a single report after all checks complete.
+
+## Summary Table
+
+```
+Planning Health Check
+=====================
+
+[PASS]  Structure           .planning/ exists, all required files present
+[FAIL]  Config              config.json missing required field `depth`
+[PASS]  Phase consistency   Directories match ROADMAP.md phases
+[PASS]  Plan/Summary        All pairings valid
+[FAIL]  STATE.md accuracy   Phase reference is stale
+[PASS]  Frontmatter         All PLAN/SUMMARY files have valid frontmatter
+[PASS]  ROADMAP/STATE sync  ROADMAP and STATE phase statuses are consistent
+[PASS]  Hook log            No recent hook errors
+[PASS]  Config completeness All expected fields present
+```
+
+## Status Indicators
+
+| Indicator | Meaning | Counts as Issue? |
+|-----------|---------|-----------------|
+| `[PASS]`  | Check passed, no problems | No |
+| `[FAIL]`  | Required condition violated | **Yes** |
+| `[WARN]`  | Recommended condition violated | No |
+| `[INFO]`  | Informational note | No |
+
+## Issues Section
+
+Only shown when at least one FAIL exists:
+
+```
+Issues Found: {count}
+---------------
+
+1. {problem description}
+   File: {file path}
+   Fix:  {concrete fix suggestion}
+
+2. {problem description}
+   File: {file path}
+   Fix:  {concrete fix suggestion}
+```
+
+## Recent Decisions (Bonus)
+
+If `.planning/logs/decisions.jsonl` exists, show the last 5 entries:
+
+```
+Recent Decisions:
+- {date}: {summary} (phase {N})
+- {date}: {summary} (phase {N})
+```
+
+If the file does not exist, skip silently.
+
+## Final Line
+
+- With issues: `Result: {N} issues found. Review and apply fixes manually.`
+- All passed: `Result: All checks passed. Planning directory is healthy.`