ng-close-packet

ng-close-packet

Portable command prompt generated from skills/closing-stale-packets/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.

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.

Use when

• ng status reports a scaffold or invalid packet 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.

Do not use when

• 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 an invalid packet.

Prompt text

Bring a stale Nuclear-grade change packet to an honest terminal state.

Inputs:
- ng status output (packet name, mode, health tag):
- packet path (.nuclear/changes/<slug>):
- originating issue / PR / anchor:
- is the underlying change still wanted? yes / no / unknown:

Do this:
- Establish ownership and intent before acting.
- Choose exactly one terminal state:
  - COMPLETE: change is still wanted; fill the prompts that matter, remove the
    placeholder marker because the packet is filled, and make validate pass.
  - CLOSE: change was deliberately abandoned; add a `NUCLEAR-GRADE-CLOSED:` marker
    line with the rationale (why dropped, what replaced it if anything, who decided)
    and keep the packet as a record. `ng status` then reports it as `closed`.
  - DELETE: it was never a real change (empty scaffold, nothing to learn); remove
    the directory so it stops looking like work.
- Prefer CLOSE over DELETE when any rationale is worth preserving.
- Do not fake a pass by deleting the marker on an unfilled packet.

Return the chosen state, the closure note (for CLOSE), and confirmation that
ng status no longer shows an unexplained scaffold or invalid packet.
Do not imply formal assurance, compliance, certification, safety, security, or regulatory adequacy.