Menu
SkillsMP has collected 10 skills from akornmeier/super-agent-teams-plugin. Open a skill to review its source and details.
Showing 10 of 10 collected skills.
Use when a bug, stack trace, failing test, or regression is reported ("X is broken", "crash on Y", "failing since Z"). Creates a `pipeline` debug team — researcher → debugger → reviewer-correctness → developer → tester — coordinated through a `TaskList`…
Use when code has been written and needs multi-lens critique ("review this", "audit", "check the PR", "lint this change"). Creates a `parallel-panel` review team with three named teammates (`reviewer-architecture`, `reviewer-correctness`, `reviewer-security`)…
Use when the user wants a plan taken to implemented+reviewed+tested in one shot ("ship it", "full cycle", "end-to-end", "take the plan to green"). Creates a `staged-team` whose members rotate per stage — work → review → test — so each downstream stage checks…
Use when an approved plan doc exists and the user wants code written ("implement the plan", "build phase 2", "code this up"). Parses the plan to classify frontend/backend/full-stack. Frontend-only and backend-only paths run as a `solo` developer dispatch;…
Use when the user has selected an idea from an ideation doc (or names a concrete feature directly) and needs it expanded into user stories and acceptance criteria. Produces `docs/brainstorms/<YYYY-MM-DD>-<slug>-requirements.md` with Given/When/Then criteria,…
Use at the end of a full cycle (after `/ship` or `/debug`) to harvest the run into durable signal — a solution doc in `docs/solutions/<category>/` plus curated memory files. Dispatches `docs-writer` then `/memory-curate` for families near the soft limit.…
Use when the user asks to explore options, brainstorm directions, or propose approaches for a fuzzy problem ("what could we do about X", "propose", "spitball", "ideas for"). Produces a ranked set of 3–5 scored ideas in `docs/ideation/<YYYY-MM-DD>-<slug>.md`…
Use when an agent's memory file has exceeded the soft or hard character limit and needs consolidation. Runs three stages in order — dedupe, score-and-drop, summarize — and stops as soon as the file is under the soft limit. Invoked by the orchestrator when…
Use when requirements exist (from `/brainstorm`) or the user asks for a technical design, ADR, or implementation plan. Produces `docs/plans/<YYYY-MM-DD>-<slug>-plan.md` conforming to `references/plan-schema.md`, reviewed once by `reviewer/architecture` for…
Use when new code needs test coverage or when asked to "write tests", "cover this", or "add integration tests". Runs `tester/unit` and `tester/integration` in parallel against the implementation diff, writes test files, and produces a merged coverage-gap…