library-wasp-drone — Claude Code subagent: usage & setup
library-wasp-drone manages repo documentation lifecycle, scaffolding library/ folders and turning issues or specs into IRDs and PRDs.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat library-wasp-drone does
This subagent structures repository docs under a schema v2 layout in library/. It organizes public guides, architectural records, and product requirements. Instead of editing frontmatter tags, the agent signals status by moving complete feature directories across backlog/, in-work/, and completed/. Feature PRDs use sequential local numbers, while issue records match existing issue numbers from GitHub.
The agent never touches library/notes/, leaving that folder for manual developer notes. Audit writeups are reserved for quality-wasp-drone, so QA reports cannot be requested directly here. Shared contract terms also belong to a dedicated peer agent.
If a bug does not exist on GitHub, the agent will refuse to generate an IRD folder for it.
What it helps with
- scaffold a schema v2 documentation hierarchy in
library/ - turn technical requirements into a structured feature PRD
- reverse-engineer legacy code into a backwards PRD
- convert GitHub issues into traceable IRD records
- audit repository documentation for drift against code
Example prompts for the agent
- Initialize the library documentation structure
- Write a PRD for the billing integration
- Run a documentation sync audit to check for drift
How to install library-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install wasp-nest-core@wasp-nest2Manually: put the files in place
.claude/agents/library-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/library-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/library-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about library-wasp-drone
How to install library-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools followed by /plugin install wasp-nest-core@wasp-nest. Agent configuration can also be stored directly in .claude/agents/library-wasp-drone.md.
Can library-wasp-drone write QA reports?
No. The agent maintains the qa/ folder layout within requirement paths, but drafting QA findings is strictly reserved for quality-wasp-drone.
Why are GitHub issues required for IRDs?
The schema binds every IRD identifier directly to a GitHub issue number. The agent does not create incident records without a matching issue.