plan: post-planning gap report (fill the plan-gaps.md stub) #18
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tier: PORT (genuine gap) · single small artifact
Add a post-planning gap report (GSD-core
gap-analysis). Todaycad-auditcatches dropped requirements only pre-ship. A read-only Source|Item|Status table run the moment/cad-planfinishes 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.mdworkflow stub. This issue is the content for it.Source: internal GSD comparison note, 2026-07-18.
Won't do. The premise is stale:
cadence-core/workflows/plan-gaps.mdis no longer a stub waiting for content, it is the--gapsUAT-closure branch, a different feature. And v1.4.0 moved the ground under the request, since/cad-plannow seeds Pending REQUIREMENTS traceability rows at plan time viaplanning.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.