Menu
[DEPRECATED] Use sw:team-lead --preset <name> instead.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | sw/team-build |
| description | [DEPRECATED] Use sw:team-lead --preset <name> instead. |
| version | 1.0.0 |
| allowed-tools | Read |
Deprecated:
sw:team-buildis deprecated. Usesw:team-lead --preset <name>instead. This skill will be removed in SpecWeave v1.3.0.
Replace:
/sw:team-build <preset-name>
With:
/sw:team-lead --preset <preset-name>
The same preset names from team-build are available via --preset:
full-stack — frontend + backend + database + testing agentsapi-only — backend + database + testing agentsfrontend-only — frontend + testing agentsmicroservice — backend + testing + devops agentsWrite 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".
Analytics and metrics for SpecWeave usage — token consumption, cache efficiency, agent spawn counts.
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".
[DEPRECATED] Use `sw:multi-project --tool github` instead. Organizes specs and splits tasks across multiple GitHub repositories. This skill will be removed in SpecWeave v1.3.0.
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] GitHub issue formatting standard. See docs/internal/specs/github-issue-standard.md