You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that PRs will be rejected if the linked issue does not have status:approved
🔍 Affected Area
Other
💡 Problem Statement
#4967 (e219644, feat(workflow)!: retire SDD and OpenSpec in favor of ODD) removed the SDD machinery from main, and its tracker #4959 is closed. The retirement did not sweep the backlog: 40 open threads (12 issues, 28 PRs) still ask for fixes, features, or docs whose entire scope no longer exists on main.
Verified on current org main: internal/sddstatus/, skills/sdd-*, the 11 SDD phase-agent overlays, openspec/, sdd_attempt, and every assets/*/sdd-orchestrator.md are gone (0 files each). The only remaining SddTaskResult reference is TestRetiredSDDTaskResultAxisIsNotRegistered, a guard test asserting the retired axis stays unregistered.
Every item below was checked against its body: the full ask lives inside deleted SDD machinery. Threads that only mention SDD but track surviving defects are listed under "Keep open" so they are not swept by mistake.
📦 Proposed Solution
A maintainer closes the following as not planned (obsoleted by the SDD retirement), referencing this tracker.
Commenting on each of the 40 threads individually: rejected, since all items share one mechanical root cause and one reference commit, and 40 separate notifications are harder to review than one list. Doing nothing leaves 40 threads that cannot be fixed as written.
📎 Additional Context
Method: full scan of all 688 open issues and 217 open PRs on 2026-09-26 (keyword filter on title and body, then per-thread reading with evidence quotes), grounded against post-retirement org/main. Per-thread evidence quotes available on request.
Pre-flight Checklist
status:approved🔍 Affected Area
Other
💡 Problem Statement
#4967 (e219644,
feat(workflow)!: retire SDD and OpenSpec in favor of ODD) removed the SDD machinery from main, and its tracker #4959 is closed. The retirement did not sweep the backlog: 40 open threads (12 issues, 28 PRs) still ask for fixes, features, or docs whose entire scope no longer exists on main.Verified on current org main:
internal/sddstatus/,skills/sdd-*, the 11 SDD phase-agent overlays,openspec/,sdd_attempt, and everyassets/*/sdd-orchestrator.mdare gone (0 files each). The only remainingSddTaskResultreference isTestRetiredSDDTaskResultAxisIsNotRegistered, a guard test asserting the retired axis stays unregistered.Every item below was checked against its body: the full ask lives inside deleted SDD machinery. Threads that only mention SDD but track surviving defects are listed under "Keep open" so they are not swept by mistake.
📦 Proposed Solution
A maintainer closes the following as not planned (obsoleted by the SDD retirement), referencing this tracker.
Issues (12):
## SDD Session Preflightblock both deleted)PRs (28):
fix/3043-*branches (diff vs main is the whole tree; the feat(opencode): extend the SDD orchestrator with native background subagents #3043 feature is deleted)Follow-ups after closing:
sdd-orchestrator.mdassets that no longer exist, so both fixes need re-landing on the ODD surfaces.Keep open (do NOT close):
🔄 Alternatives Considered
Commenting on each of the 40 threads individually: rejected, since all items share one mechanical root cause and one reference commit, and 40 separate notifications are harder to review than one list. Doing nothing leaves 40 threads that cannot be fixed as written.
📎 Additional Context
Method: full scan of all 688 open issues and 217 open PRs on 2026-09-26 (keyword filter on title and body, then per-thread reading with evidence quotes), grounded against post-retirement org/main. Per-thread evidence quotes available on request.