packet-factory
Packet Factory enforces a gatekeeper model where every task with side effects requires an APPROVED packet before running. Create packets in DRAFT status, review them for approval or rejection, then dispatch only approved work. Once approved, scope is locked to prevent creep—expansions spawn new packets instead.
Packet Factory creates and manages atomic work packets with mandatory approval gates before any task execution.
AI-generated summary based on this skill's SKILL.md
Install
open-gitagent/opengap/packet-factory · repository language: TypeScript
git clone https://github.com/open-gitagent/opengap
cp -r opengap/examples/jason-my-claw-is-the-law-deebee-4567b4/skills/packet-factory ~/.claude/skills/packet-factoryFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create a new packet in Packet Factory?
Packet Factory lets you create work packets in DRAFT status as atomic units of work. Start by defining your task scope, parameters, and any side effects. Once created, the packet enters the review queue where it awaits approval or rejection before execution can proceed.
What is the packet factory workflow management process?
Packet Factory enforces a gatekeeper model with four stages: create packets in DRAFT status, review them for scope and side effects, approve or reject them, then dispatch only approved work. This workflow ensures every task with side effects gets explicit authorization before running.
How does Packet Factory prevent scope creep with packets?
Packet Factory locks packet scope immediately after approval—no modifications allowed. If requirements expand, you create a new packet instead of altering the approved one. This immutable scope mechanism ensures approved work stays bounded and prevents unauthorized expansions.
Can Packet Factory review and approve work packets?
Yes. Packet Factory provides a review interface where you examine packet details, validate side effects, and make approval or rejection decisions. Only approved packets can be dispatched for execution, giving you full control over which atomic work units run.
How does Packet Factory manage draft packets and escalate stale ones?
Packet Factory tracks in-flight packets and monitors drafts that remain unapproved. Stale drafts can be escalated to ensure timely review and prevent work from languishing in the queue. This keeps your packet workflow moving and maintains visibility over pending approvals.
What makes Packet Factory suitable for atomic task packets with side effects?
Packet Factory is designed for tasks that modify state or trigger external actions. Its approval-gate model ensures side effects only execute after explicit authorization. Each packet is atomic—a complete, reviewable unit—making side effect execution controlled and auditable.
SKILL.md
rendered from the published skill — quoted content, verbatim
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
examples/jason-my-claw-is-the-law-deebee-4567b4/skills/packet-factory/SKILL.md