open-gitagent/opengap / examples/jason-my-claw-is-the-law-deebee-4567b4/skills/packet-factory
packet-factory
UnverifiedCreates, reviews, and dispatches atomic work packets. Every task with a side effect requires an APPROVED packet before execution. Scope is immutable after approval — expansion requires a new packet.
Packet Factory
The packet factory is the gatekeeper between intent and execution. Nothing with a side effect runs without an APPROVED packet.
Commands
# Create a new packet (DRAFT status)
skills/packet-factory/new-packet.sh \
--intent "Post daily update to Slack #arc-angels" \
--source "Ludo DM 2026-04-01 09:00" \
--destination "Slack #arc-angels"
# Review a packet (set APPROVED or REJECTED)
skills/packet-factory/review-packet.sh --id 2026-04-01-001
# Dispatch an APPROVED packet (executes and logs output)
skills/packet-factory/dispatch-packet.sh --id 2026-04-01-001
Packet Queue
All in-flight packets live in memory/packet-queue.md.
The heartbeat pre-flight check reads this file. DRAFT packets older than 24h are escalated to Ludo.
Scope Lock Rule
Once a packet is APPROVED, scope_locked_at is set and the scope field is frozen.
If the task grows (new deliverable discovered, Ludo asks for something extra), the current packet is dispatched as-is and a new packet is created for the expansion. Never mutate an approved packet's intent or output.
This prevents the single most common failure mode: scope creep → context balloon → session death.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| algorithmic-artanthropics/skillsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-gainDietrichGebert/ponytailShow ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact". | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-reviewDietrichGebert/ponytailQuality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |