_{Want to know what will actually drive more revenue? OSPRY is the insight engine built for exactly that.}

Start here

Install Claude Code or Codex, then add the public marketplace. In Claude Code, enter these in the assistant's command prompt:

/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nest

In a terminal with Codex installed, add the same marketplace and select the core in the plugin browser:

codex plugin marketplace add legioncodeinc/vibe-coding-tools
codex plugin add wasp-nest-core@wasp-nest

The v3 layout has a required Core and the optional plugins declared in its current catalog. Purge the previous Wasp Nest installation before installing it. Keep Core enabled and select each workflow's prerequisites.

Choose the packs your work needs. Claude skills use their plugin namespace, such as /wasp-nest-core:get-started-stinger; Codex shows skills and command wrappers. Native Codex Drone roles require Core's trusted hook and an explicit registry of enabled package roots. The local installer writes that registry; a marketplace install alone is not proven to do so. Review the selection before trusting /hooks and starting a new session. See harness capabilities.

Open the repository you want to work on and ask:

Use the Get Started Stinger to inspect this repository. Explain the home instruction setup and the project Library setup, ask before changing either, and show me the resulting diff and setup report.

The first-session hook checks home and project setup locks on supported local hosts. Missing setup prompts an offer. Existing code gets a Knowledge pass before Library setup completes. Read Getting Started before accepting either offer.

The problem this fixes

Your assistant can write code. It still needs your product facts, past decisions and definition of done.

Drones own bounded specialties. Stingers carry methods, examples and cited research. The Library keeps knowledge, plans, issue fixes and shared contracts for the next agent. You can check the work against written decisions.

The Library is the workbench

The Library holds current facts and future plans in your project. Get Started offers setup after consent; Knowledge documents existing code first. Human-only library/notes/ is not agent input.

Learn why the Library exists, write a PRD or IRD, and agree on a CTR. Draft contracts block dependent work.

From request to reviewed code

flowchart TD
    A["New request"] --> B{"What kind of work?"}
    B -- New product --> PS["/plan-product: strategy, design, wave plan, Definition of Done"]
    PS --> P
    B -- New behavior --> P["Library writes a PRD with acceptance criteria"]
    B -- Tracked bug --> I["Library writes an IRD"]
    B -- Scoped task --> R["Call /pest-controller"]
    P --> C{"Shared boundary across plans?"}
    C -- Yes --> D["Contract Writing drafts CTR-###"]
    D --> E{"Exact revision accepted?"}
    E -- No --> W["Dependent work waits; unrelated work continues"]
    E -- Yes --> PIN["Library pins the revision in each PRD"]
    PIN --> S["Call /smoke-it"]
    C -- No --> S
    I --> R
    S --> L["Acceptance ledger and the approved wave plan"]
    L --> CODE["Drones read Stingers, code, and test"]
    R --> CODE
    CODE --> V["Verify against the PRD, IRD, or task"]
    V --> G["Security then quality; Ship Gate on demand"]
    G --> H["Owner authorizes commit and push"]
    H --> PR["Pull request, CI, and review"]

/smoke-it is the full PRD execution path. It selects Drones from the roster itself, so you do not need to call /pest-controller first. Use /pest-controller to route a bounded task or IRD fix. Smoke It includes security and quality close-out; /ship-gate is the on-demand gate for a scoped diff. Neither command grants permission to commit, push, or deploy.

For parallel PRDs, one accepted contract revision is the handoff:

flowchart LR
    B[Shared boundary found] --> C[Contract Writing drafts CTR-###]
    C --> A{Exact revision accepted?}
    A -- No --> W[Dependent work waits]
    A -- Yes --> P1[Library pins PRD A]
    A -- Yes --> P2[Library pins PRD B]
    P1 --> X[Provider work]
    P2 --> Y[Consumer work]
    X --> T[Checks against same CTR revision]
    Y --> T

A Draft or disputed contract blocks the dependent boundary. The learning path has the document-authoring guides, worked example, and more diagrams.

What to call

Short Core commands use /wasp-nest-core: in native Claude. Optional commands show their owning prefix below. Use your client's exact selector; local home installations also expose flat commands.

These are Claude entry points. Other clients use supported Stingers or command wrappers. TARS, CASE and KIPP have no Codex, Cursor or Cowork fallback; they require Claude Code Desktop. Invocation does not authorize external actions.

Keep Core installed alongside each owning plugin. Choose a document workflow for prerequisites, sample requests and the difference between preparing an app, refreshing its knowledge and explaining it to readers. Use /wasp-nest-core:forge for a new reusable component; public correction requests belong in the issue tracker below.

The parts, in plain English

The Drone and Stinger pairing is enforced by the source validator. A missing pairing is not silently shipped.

What ships

Marketplace release v3.0.0. The core and add-on packs have independent manifest versions; counts and descriptions below are read from the built plugins, not maintained by hand.

The Claude catalog and Codex catalog expose these packs individually. Runtime guides and research distillations ship with them. Raw research archives, node_modules/, and ingested photography models do not. The photography pack retains only its blank model template.

The complete plugin catalog lists every shipped Stinger, Drone and command by pack with purposes and direct instructions. The hook catalog covers shared hooks and their host limits.

Learn and build on it

• How We Build (branded PDF): the whole workflow from idea to shipped, in plain language.
• Getting Started: install, consent, and first project setup.
• Components: Drones, Stingers, commands, rules, and hooks.
• Write a PRD, IRD, or CTR, then execute the plan with evidence.
• Document workflows: Library Packets, App Primer Zero and KB Refresh with example requests.
• Model Selection, Security and Secrets, and Troubleshooting.

This repository is generated from canonical source. Open an issue for corrections or component requests. Maintainers change the source with Queen Wasp and validate it before release.

License and attribution

The Wasp Nest is created by Mario Aldayuz and Legion Code Inc.. First-party material is licensed under AGPL-3.0-or-later. Embedded third-party material retains its own rights; see third-party notices and each pack's notices. This license replaces prior repository-specific usage terms.

Built for vibe coders. Go ship something you can prove works.

_{We are Legion. Vibe with Legion.}