Skip to content

forgeplan blindspots

Find blind spots — active decisions that have no evidence backing them (R_eff = 0) and orphan artifacts not linked to any parent. This is the most important health-triage command: an active PRD/RFC/ADR without evidence is a “false promise” — a decision that looks real but has no measurement behind it.

  • Session start — run this right after forgeplan health and fix before starting new work (do not accumulate debt)
  • CI gate — fail the build if any active critical artifact has no evidence
  • Pre-release — zero blind spots before cutting a tag
  • Retro — count how many blind spots accumulated over the sprint
forgeplan blindspots
-h, --help Print help
-V, --version Print version

Print all blind spots:

Terminal window
forgeplan blindspots

Use as a CI gate (exits non-zero on any blind spot):

Terminal window
forgeplan blindspots || exit 1

Combined with health --ci for full gating:

Terminal window
forgeplan health --ci && forgeplan blindspots

Two sections — blind decisions and orphans:

BLIND DECISIONS (active, R_eff = 0.00)
PRD-046 Docs v0.18.0 catch-up → create EvidencePack + link
ADR-008 Cloudflare Pages choice → create EvidencePack + link
ORPHANS (no parent)
PRD-044 Unused PRD → link to Epic or deprecate
NOTE-031 One-off observation → link to artifact or ignore
Summary: 2 blind decisions, 2 orphans
SectionWhat it means
Blind decisionsActive PRD/RFC/ADR with R_eff = 0 (no evidence)
OrphansArtifact with no parent and no inbound link

Exit code: 0 if clean, 1 otherwise. Use this in git pre-push hooks or CI.

blindspots is a strict subset of what health reports — extracted as a standalone command because it is the most common gate to enforce. The unified workflow mandates:

session start → health → blindspots → (fix) → new work

If blindspots is not empty, fix it first. Never let active decisions drift without measurement — that is exactly what the R_eff weakest-link model is designed to prevent.