{"enrichment":{"faq":[{"a":"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.","q":"How do I create a new packet in Packet Factory?"},{"a":"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.","q":"What is the packet factory workflow management process?"},{"a":"Packet Factory locks packet scope immediately after approval\u2014no 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.","q":"How does Packet Factory prevent scope creep with packets?"},{"a":"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.","q":"Can Packet Factory review and approve work packets?"},{"a":"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.","q":"How does Packet Factory manage draft packets and escalate stale ones?"},{"a":"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\u2014a complete, reviewable unit\u2014making side effect execution controlled and auditable.","q":"What makes Packet Factory suitable for atomic task packets with side effects?"}],"shadow_tags":["task-gating","scope-immutability","work-unit-lifecycle","approval-workflow","side-effect-control","packet-queue","execution-governance","scope-creep-prevention","atomic-operations"],"summary_rewrite":"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\u2014expansions spawn new packets instead."},"files":[{"bytes":1471,"path":"examples/jason-my-claw-is-the-law-deebee-4567b4/skills/packet-factory/SKILL.md","sha256":"86df1647ffe12b18be0b1076f31ac4fa0ad8f9eb41ad72d65c74ff823dd55f5e","url":"https://skillfed.io/files/open-gitagent/opengap/packet-factory/822fc011/SKILL.md"}],"id":"open-gitagent/opengap/packet-factory","links":{"html":"https://skillfed.io/open-gitagent/opengap/packet-factory","md":"https://skillfed.io/open-gitagent/opengap/packet-factory.md","repo":"https://github.com/open-gitagent/opengap"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":343,"language":"TypeScript","last_updated":"2026-07-02","license":"MIT","name":"packet-factory","publisher":"open-gitagent","stars":2903},"relations":{"similar":[{"id":"open-gitagent/opengap/narco-check"},{"id":"open-gitagent/opengap/get-started"},{"id":"open-gitagent/opengap/export-agent"},{"id":"open-gitagent/opengap/run-agent"},{"id":"open-gitagent/opengap/manage-skills"},{"id":"open-gitagent/opengap/web-search"},{"id":"open-gitagent/opengap/create-agent"},{"id":"open-gitagent/opengap/code-review"},{"id":"open-gitagent/opengap/paper-search"},{"id":"open-gitagent/opengap/knowledge-retrieval"}]},"slug":{"owner":"open-gitagent","repo":"opengap","skill":"packet-factory"},"version":"822fc011"}