--- name: "library-packets-stinger" description: "Turn a library into cited audience packets in Markdown, Word and branded PDF. Use for executive, public, sales, service or engineering documents grounded in existing sources." license: AGPL-3.0-or-later compatibility: "Claude Code desktop, Claude Cowork, ChatGPT Codex desktop; plain ChatGPT with accessible files and document tools. Python 3.10 or newer for helpers." metadata: hive-drone: "library-packets-wasp-drone" pair-drone: "library-packets-wasp-drone" domain: "Evidence-grounded document packets" --- # Library Packets Stinger Read [README.md](README.md) for the guide map. The paired [Drone](../../agents/library-packets-wasp-drone.md) owns packet production from the selected library. ## Purpose Create extensive, useful audience documents when the source material supports them. Each selected document receives Markdown, editable Word, PDF and citations. Use the real Legion Code Inc. icon and word mark in the footer. Missing facts produce coverage gaps and specific questions, never invented content. ## When to use - Turn a supplied PRD into a plain-language reader packet while preserving actors, permissions, sequence and Draft/Accepted/current/target status. Apply [the PRD guide](guides/08-explain-prd-with-constraints.md) and [preservation ledger](templates/prd-preservation-ledger.md) before the existing format/render/page-review steps. - Turn this library into founder, investor, public or team documents. - Produce a source-grounded product atlas, sales/support packet or engineering handoff. - Build branded Markdown, Word and PDF packets with traceable citations. ## When not to use - A bounded in-chat explanation without document export: resolve the selected Developer Learning `technical-explainer-stinger`. Library Packets retains source-grounded audience packet and format production ownership. - Scaffolding or changing source PRDs/IRDs: use Library Stinger. - Writing internal architecture knowledge only: use Knowledge Stinger. - A competitive workbook alone: use Competitive Research Stinger. - Publishing, messaging, deployment, source modification or implementation of proposed features: obtain the relevant task authority and specialist. ## Procedure 1. Ask only the unresolved [intake questions](references/intake.md). Confirm source access, readers, decisions, product account, public exclusions, research, branding and outputs. Check the [desktop capability boundary](guides/07-desktop-portability.md). 2. [Inventory and read](guides/02-read-and-map-evidence.md) the library. Build a source/claim/coverage ledger and select supported types from the [catalogue](references/document-catalogue.md). Defer unsupported core documents without padding. 3. [Research and decide](guides/03-research-and-decide.md) within authorized scope. Use current primary sources, accurate dates and feature-focused collection. Give competitive packets an executive decision, defensible edges and buildable gaps. 4. [Write for each reader](guides/04-write-for-the-reader.md). No em dashes, filler or wordy explanations. General prose targets grade 8; engineering retains needed detail. Preserve actor/action limits. Public prose omits technical/internal disclosures. 5. [Build all formats](guides/05-build-the-packet.md) from one reviewed model using the available tools and [helper contract](scripts/README.md). Use the approved real logo. Keep private evidence separate from public files and citations. 6. [Inspect every final page](guides/06-review-and-deliver.md), including Word render, PDF, references and footer. Tie the actual review to current hashes. No passing attestation without inspection; missing formats or unresolved findings remain incomplete. 7. Deliver the reader index and supported documents with citations, plus the private coverage/gap and verification records to their authorized audience. Do not commit, publish or send the packet automatically. ## References map - [Evidence and public boundaries](references/evidence-and-publication.md): load before claims or public writing. - [Coverage template](references/coverage-template.csv) and [brief template](references/brief-template.md): adapt only to supported content. - [Domain distillation](references/research/distilled-library-packets.md): 28 cited primary facts, owner rules and derived workflow choices; the raw archive supplies original bodies. - [Portable ChatGPT starter](references/chatgpt-starter.md): use where no native command/agent selector exists. - [Asset provenance](assets/PROVENANCE.md): original footer icon/word mark and rendered PNG. - [Packet tools](scripts/README.md): inventory, validate, render and hash-bound review completion. Runtime packet production is research-only. It changes no application source or accepted contract. Ship Gate removed for runtime document production; commits or publication remain separately authorized actions. ## Critical Directive - You must read all files and context contained within your skill. - In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task. - Additional related skills can be found here: - [knowledge-stinger](https://github.com/legioncodeinc/vibe-coding-tools/blob/main/plugins/wasp-nest-core/skills/knowledge-stinger/SKILL.md) - Narrative source knowledge and architecture context. - [competitive-research-stinger](https://github.com/legioncodeinc/vibe-coding-tools/blob/main/plugins/growth-and-customer-tools/skills/competitive-research-stinger/SKILL.md) - Primary competitor research and evidence-backed edges. - [technical-writing-craft-stinger](https://github.com/legioncodeinc/vibe-coding-tools/blob/main/plugins/wasp-nest-core/skills/technical-writing-craft-stinger/SKILL.md) - Reader-focused writing and editorial review. - [library-stinger](https://github.com/legioncodeinc/vibe-coding-tools/blob/main/plugins/wasp-nest-core/skills/library-stinger/SKILL.md) - Source library lifecycle, PRDs and IRDs.