plan: post-planning gap report (fill the plan-gaps.md stub) #18

Closed
opened 2026-07-18 22:05:18 +00:00 by crenshawdev · 1 comment
crenshawdev commented 2026-07-18 22:05:18 +00:00 (Migrated from github.com)

Tier: PORT (genuine gap) · single small artifact

Add a post-planning gap report (GSD-core gap-analysis). Today cad-audit catches dropped requirements only pre-ship. A read-only Source|Item|Status table run the moment /cad-plan finishes catches a silently-dropped requirement at the cheapest possible moment.

Why: "gates are real gates" at the cheapest point. Zero machinery.

Cost: Cadence already has a plan-gaps.md workflow stub. This issue is the content for it.

Source: internal GSD comparison note, 2026-07-18.

**Tier:** PORT (genuine gap) · single small artifact Add a **post-planning gap report** (GSD-core `gap-analysis`). Today `cad-audit` catches dropped requirements only *pre-ship*. A read-only Source|Item|Status table run the moment `/cad-plan` finishes catches a silently-dropped requirement at the cheapest possible moment. **Why:** "gates are real gates" at the cheapest point. Zero machinery. **Cost:** Cadence already has a `plan-gaps.md` workflow stub. This issue is the content for it. _Source: internal GSD comparison note, 2026-07-18._
crenshawdev commented 2026-07-28 17:11:50 +00:00 (Migrated from github.com)

Won't do. The premise is stale: cadence-core/workflows/plan-gaps.md is no longer a stub waiting for content, it is the --gaps UAT-closure branch, a different feature. And v1.4.0 moved the ground under the request, since /cad-plan now seeds Pending REQUIREMENTS traceability rows at plan time via planning.mjs seed-reqs, which covers the silently-dropped-requirement case at the cheap moment this issue was aiming for. Not carrying it into the next milestone.

Won't do. The premise is stale: `cadence-core/workflows/plan-gaps.md` is no longer a stub waiting for content, it is the `--gaps` UAT-closure branch, a different feature. And v1.4.0 moved the ground under the request, since `/cad-plan` now seeds Pending REQUIREMENTS traceability rows at plan time via `planning.mjs seed-reqs`, which covers the silently-dropped-requirement case at the cheap moment this issue was aiming for. Not carrying it into the next milestone.
Sign in to join this conversation.
No description provided.