Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Validate that all Discovery artefacts (Epics, Stories) are clear, governed, complete, and safe to pass into Delivery. Activate after generating Epics or Stories and before any Delivery planning. This is the mandatory Discovery → Delivery gate.
Batch-close all complete increments by delegating each one to `sw:done`. Discovers active/ready-for-review increments with zero pending tasks, then iterates and calls `sw:done` per increment. Use when saying "close all", "close stuck increments", or "batch close".
Decomposes goals into team blueprints using evidence-based scaling laws, topology selection, and role design. Determines whether a goal needs a single agent or a coordinated team (3-4 agents recommended, 5 max), selects the optimal communication topology (sequential pipeline, parallel-independent, centralized coordinator, hierarchical), and produces structured blueprints with artifact chains and quality gates. Use this skill when the user wants to build something, plan a project, assemble a team, figure out what roles they need, break down a complex goal, or asks "how should I approach [X]?" — even if they don't mention agents or teams. Also triggers on specific domains: "build a SaaS," "marketing campaign," "security audit," "write a book," "launch a product." Do NOT use for simple single-step tasks, direct coding questions, or file operations that need no planning.
Write a portable, secret-scrubbed work handoff doc so you can continue this work in any AI tool. Use when saying "handoff", "running out of tokens", "switch to Codex/OpenCode/Gemini/Cursor", "continue elsewhere", or "continue on another machine".
Unified multi-project management skill for GitHub, Azure DevOps, and Jira. Organizes specs and splits tasks across multiple repositories or projects for monorepo, polyrepo, project-per-team, and area-path architectures. Use `--tool github|ado|jira` to select the target integration.
[DEPRECATED] Use sw:team-lead --preset <name> instead.
Restore session context from session-notes.md at the start of a new session. Auto-continues if Next Action is specific enough.
Use when a task involves continuing a project, restoring project context, maintaining file-based project memory, updating current-state summaries, or recording meaningful progress across sessions. Works best for long-horizon, file-based projects and supports research writing, product document collaboration, software project coordination, and broader cross-functional project continuity.
Run a quick session retrospective: what worked, what didn't, lessons learned.