The Wasp Nest is easiest to understand in three passes: install a plugin, learn what each component owns, then use the Library to define work before dispatching a Drone. You can enter this guide at any page. Each page names its purpose and links to the operational component when you need its exact instructions.
- Get started with a public marketplace install and the two separate setup offers.
- Understand the pieces, then try one bounded request with Pest Controller.
- Set up the Library and learn why its documents exist.
- Write a PRD for planned behavior, write an IRD for a tracked defect, or agree on a CTR before parallel work shares an interface.
- Execute a PRD with acceptance criteria and evidence.
| Question | Read |
|---|---|
| Why use a specialist and how is one scoped? | Drones |
| What does a reusable skill contain? | Stingers |
| How do named workflows route or close work? | Commands |
| Which guidance stays active? | Rules |
| What runs at a lifecycle event? | Hooks |
| What can each coding harness actually load? | Harness capabilities |
The glossary defines Wasp Nest terms. The complete plugin catalog links every shipped Drone and Stinger without making this learning path a 300-item roster.
- Model selection explains matching a scoped task to a model, without changing its authority.
- Security and secrets separates learning examples from live credentials and external effects.
- Troubleshooting covers missing packs, commands, and onboarding prompts.
Worked learning examples connect a PRD, an accepted CTR revision, implementation evidence, and an IRD without pretending those examples are a live project's plans. The canonical Get Started Library templates, Library examples, and Contract Writing handoff remain with their plugins. This learning section teaches them; it does not maintain second copies that can drift.
The public marketplace is generated from private source. If a guide is unclear or a pack needs a new example, open an issue with the page and the step that confused you.