# library-wasp-drone

library-wasp-drone manages repo documentation lifecycle, scaffolding library/ folders and turning issues or specs into IRDs and PRDs.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/agents/library-wasp-drone.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/library-wasp-drone

## What it 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.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install wasp-nest-core@wasp-nest
```

2. **Manually: put the files in place**
- File: `.claude/agents/library-wasp-drone.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/library-wasp-drone.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/library-wasp-drone.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/agents/library-wasp-drone.md

## When to use it
- 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
- Initialize the library documentation structure
- Write a PRD for the billing integration
- Run a documentation sync audit to check for drift

## Similar
- [Create PRD Chat Mode](https://affpapa.org/en/nevibecode/agents/create-prd-chat-mode.md) — subagent · ★ 41430 repo stars
- [project-planning](https://affpapa.org/en/nevibecode/plugins/project-planning.md) — plugin · ★ 41430 repo stars
- [pm-advisor](https://affpapa.org/en/nevibecode/agents/pm-advisor.md) — subagent · ★ 328 repo stars
- [scenario-report](https://affpapa.org/en/nevibecode/skills/scenario-report.md) — skill · 914 installs
- [meeting-to-tasks](https://affpapa.org/en/nevibecode/skills/meeting-to-tasks.md) — skill · 255 installs
- [printing-press-retro](https://affpapa.org/en/nevibecode/skills/printing-press-retro.md) — skill · 6800 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
