Context
Currently, the ideation-sandbox skill explicitly instructs agents to leave GitHub Discussions open after they graduate to an Epic ("The Discussion stays open as the archaeological source"). This leads to zombie threads and clutters the tracker.
The Problem
While the archaeological source must be preserved, keeping the discussion open actively harms tracker hygiene. A closed discussion is still fully accessible and searchable, but it removes the item from the active ideation queue.
The Architectural Reality
The .agent/skills/ideation-sandbox/references/ideation-sandbox-workflow.md file dictates graduation behavior.
The Fix
Update .agent/skills/ideation-sandbox/references/ideation-sandbox-workflow.md to explicitly mandate that the author MUST formally close the Discussion upon adding the GRADUATED marker.
Acceptance Criteria
- Update the Graduation Trigger section in
ideation-sandbox-workflow.md.
- Replace the instruction to keep it open with a mandate to close it.
Origin Session ID: 49e9b05a-0581-4fb7-861f-7e4970ea4c2b
Context Currently, the
ideation-sandboxskill explicitly instructs agents to leave GitHub Discussions open after they graduate to an Epic ("The Discussion stays open as the archaeological source"). This leads to zombie threads and clutters the tracker.The Problem While the archaeological source must be preserved, keeping the discussion open actively harms tracker hygiene. A closed discussion is still fully accessible and searchable, but it removes the item from the active ideation queue.
The Architectural Reality The
.agent/skills/ideation-sandbox/references/ideation-sandbox-workflow.mdfile dictates graduation behavior.The Fix Update
.agent/skills/ideation-sandbox/references/ideation-sandbox-workflow.mdto explicitly mandate that the author MUST formally close the Discussion upon adding theGRADUATEDmarker.Acceptance Criteria
ideation-sandbox-workflow.md.Origin Session ID: 49e9b05a-0581-4fb7-861f-7e4970ea4c2b