retrospective-wasp-drone — Claude Code subagent: install
The retrospective-wasp-drone subagent chooses a retro format, plans the session, and tracks action items into the next cycle when a team needs follow-through.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install business-and-product-tools@wasp-nestWhat retrospective-wasp-drone does
retrospective-wasp-drone covers the retrospective lifecycle from format choice to action-item review. It selects among formats such as Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad, DAKI, and Starfish using team context, period mood, time limits, and the sync or async setup.
The subagent runs a psychological-safety check before planning the session. It then builds a time-boxed agenda with activity prompts, voting, synthesis, and a closing action-item review. Each commitment must have an owner, a deadline, and an observable definition of done. Decisions that need documentation are handed to library-wasp-drone.
It is available for Claude Code and Codex. Claude Code uses the plugin marketplace flow, while Codex uses .codex/agents/retrospective-wasp-drone.toml. This subagent does not cover incident postmortems, which use a different method and audience.
What it helps with
- choose a retrospective format for the team’s situation
- build a time-boxed facilitation agenda
- check psychological safety before the session
- turn discussion points into owned action items
- design an async retrospective
Example prompts for the agent
- Run a retrospective and choose the format that fits our situation.
- Plan an async retro with timed activities, prompts, and a closing action review.
- Review the previous action items and help us decide what to do next.
How to install retrospective-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install business-and-product-tools@wasp-nest2Manually: put the files in place
.claude/agents/retrospective-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/retrospective-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/retrospective-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 retrospective-wasp-drone
How do I install retrospective-wasp-drone in Claude Code?
Add the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the plugin with /plugin install business-and-product-tools@wasp-nest. After that, use .claude/agents/retrospective-wasp-drone.md.
What does retrospective-wasp-drone do?
It selects a retrospective format, checks whether the team can discuss issues openly, prepares a facilitation plan, and follows action items into the next cycle.
Can I use this subagent for an incident postmortem?
No. It is scoped to retrospectives; incident postmortems follow a different methodology and serve a different audience.