closing-stale-packets
Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress packet, or to bypass validation on a packet you intend to ship.
FlyFission · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add FlyFission/nuclear-grade-context-engineering --skill closing-stale-packets技能说明
name: closing-stale-packets description: Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress packet, or to bypass validation on a packet you intend to ship.
Closing Stale Packets
Overview
A change packet that is started and then abandoned is a quiet integrity problem. It looks like work in progress, but no one owns it, its claims were never proven, and a reader cannot tell whether the change shipped, was dropped, or is still pending. ng status now surfaces these: a scaffold packet is an untouched draft still carrying the placeholder marker; an invalid packet fails validation for another reason. This skill turns that signal into a decision. Every stale packet must reach one honest terminal state: completed (filled and validating), closed (deliberately abandoned with a recorded reason), or deleted (never a real change). The forbidden state is the one most packets drift into: half-done and silent, where a green-looking directory hides an unproven claim. Closing a packet with a written rationale is a first-class successful outcome, not a failure to ship.
Decision contract
- Claim checked: every stale packet reached one honest terminal state -- completed and validating, closed with a recorded reason and decider, or deleted as a genuinely empty scaffold -- none left half-done and silent.
- Artifact observed:
ng status ./validateoutput and the packet against its originating issue/PR/anchor -> aNUCLEAR-GRADE-CLOSED:rationale line and anng status .where every packet isokorclosed. - Decision affected: block -- bring the stale packet to a terminal state so
ng statusreports ok/closed, not scaffold/invalid. - Failure class: silent-stale-packet (a half-done packet hiding an unproven claim, or a faked pass by deleting the marker).
- Next action: complete, close-with-reason, or delete; escalate to the owner before deleting any packet whose change is not confirmed dead.
When to Use
ng statusreports ascaffoldorinvalidpacket and you are deciding what to do about it.- A long or interrupted session left a packet directory behind that was never finished.
- A packet's underlying change was dropped, superseded, or merged elsewhere, but the packet still sits in
.nuclear/changes/. - A periodic cleanup or release-readiness sweep finds packets that do not map to live work.
- A packet was scaffolded to explore an idea that was then abandoned.
When Not to Use
- A packet that is actively being worked right now; it is in progress, not stale.
- A packet you intend to ship: fill and validate it, do not close it to silence the validator.
- Incident containment that must happen before housekeeping.
- The user is asking for formal assurance, certification, or regulatory approval.
Inputs
- The output of
python tools/ng.py status .(packet names, modes, and health tags). - The packet directory under
.nuclear/changes/<slug>and its files. - The originating issue, PR, or mission anchor, to tell whether the change is still live.
- The validator output (
python tools/ng.py validate .nuclear/changes/<slug>) for aninvalidpacket.
Process
- List the candidates. Run
ng status .and note every packet not taggedok. - For each stale packet, establish ownership and intent: find the originating issue, PR, or anchor, and decide whether the change is still wanted.
- Choose one terminal state, honestly:
- Complete it: if the change is still wanted, fill the prompts that matter, remove the placeholder marker, and make
validatepass. - Close it: if the change was deliberately abandoned, add a
NUCLEAR-GRADE-CLOSED:line carrying the rationale (why it was dropped, what replaced it if anything, who decided) on that same line, and keep the packet as a recorded decision.ng statusrecognizes that marker line and reports the packet asclosed, a terminal state. - Delete it: if it was never a real change (an empty scaffold from an aborted experiment with nothing to learn), remove the directory so it stops masquerading as work.
- Complete it: if the change is still wanted, fill the prompts that matter, remove the placeholder marker, and make
- Prefer close over delete when there is any decision or rationale worth preserving; prefer delete only for genuinely empty scaffolds.
- Record the closure where it will be seen: the
NUCLEAR-GRADE-CLOSED:line in the packet (for close), plus an OPEX note when the abandonment is a near miss worth learning from. - Re-run
ng status .and confirm every packet is nowokorclosed, with none left in the half-done-and-silentscaffold/invalidstate.
Outputs
- Each stale packet moved to exactly one terminal state: completed (
ok), closed, or deleted. - A
NUCLEAR-GRADE-CLOSED:rationale line recording why a packet was abandoned and who decided, for every closed packet. - An updated
ng status .in which every packet isokorclosed, with noscaffoldorinvalidpacket left needing attention. - An OPEX note when a recurring pattern of abandoned packets points to a process gap.
Verification
ng status .shows every remaining packet asokorclosed; none is left in thescaffold/invalidneeds-attention state.- Every closed packet's
NUCLEAR-GRADE-CLOSED:line names why it was dropped and who decided, not just that it was dropped. - A completed packet actually passes
python tools/ng.py validate; the placeholder marker is gone because the packet is filled, not because the marker was deleted to fake a pass. - Deleted packets were genuinely empty scaffolds, confirmed before removal.
Escalation
- Escalate to the packet's owner before deleting any packet whose change you cannot confirm is dead, since deletion is the one irreversible option.
- Escalate when stale packets accumulate faster than they are