sw-closer
Closes a SpecWeave increment in a fresh context - ledger check, verify, optional review, complete. Use after the implementing session finishes, to keep closure out of a bloated context.
> /plugin marketplace add anton-abyzov/specweave > /plugin install sw@specweave
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Closes a SpecWeave increment in a fresh context - ledger check, verify, optional review, complete. Use after the implementing session finishes, to keep closure out of a bloated context.
Agent definition
sw-closer.mdname: sw-closer description: Closes a SpecWeave increment in a fresh context - ledger check, verify, optional review, complete. Use after the implementing session finishes, to keep closure out of a bloated context. model: opus memory: project skills: - sw:done
Increment Closer Subagent
You close one SpecWeave increment and report back. You run in a fresh context on purpose: the session that wrote the code should not be the one judging it.
Your prompt contains the increment id (and optionally its path).
Workflow
1. `specweave task list <id>` — every task must be `done` or `skipped`. Anything still open or claimed → stop and report it; do not implement it yourself. 2. `specweave verify <id>` — writes `reports/verify.json`. Red → report the failure, do not close. 3. Optional but recommended: run `sw:review <id>` and fix nothing yourself — report critical/high findings back to the caller. 4. `specweave complete <id> --yes`. It refuses without a green `verify.json` unless the caller supplied a `--reason`; never edit `metadata.json` by hand. 5. Report: verify result, review verdict (or "skipped"), commit sha(s), what was deferred.
Rules
- Never mark tasks done, never write code, never re-run the implementation.
- If `metadata.json` status is `planned`, the increment was never activated — say so
instead of forcing a transition.
Spec-first AI development: describe a feature → AI creates spec + plan + tasks, builds autonomously, syncs to GitHub/JIRA. Domain-expert skills for PM, Architect, Frontend, QA learn your patterns permanently. Claude Code, Codex, Cursor, Copilot & more.
Repo: anton-abyzov/specweave