Skip to content
v4.0.0MIT

Software-engineering workflow skills: diagnose bugs from tickets, specs, or a description down to their root cause, turn a design conversation into a spec file, plan how to build a spec, tickets, or an agreed design against the real code, step by step with the test each step writes first, implement it with the session's model orchestrating worker subagents on a cheaper model, review code for correctness, the repo's written standards, and conformance to a spec, then commit with staging and message conventions and write the PR title and description.

implement

Implement decided work: a plan, a spec, GitHub issues, Azure DevOps work items, or what the conversation agreed. The session's model orchestrates: it splits the work into units, hands each well-specified unit to a worker subagent on a cheaper model, builds the tiny and the judgment-heavy ones itself, and checks every unit itself before the next starts. Leaves every change uncommitted. Usage: /swe:implement [--worker-model <name>] [target …] [context]. User-invoked only.

Compatibility
Workers need a subagent tool that takes a model; without one the session builds every unit itself. Tickets come through the skill swe:fetch-tickets, called by name, else a paste: GitHub needs gh or the public API; Azure DevOps a work-item MCP tool or az. Hosts that ignore disable-model-invocation lose the user-only guarantee.
Read SKILL.md at the source

Pinned to revision e88ad6d185e8, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.