brainstorm
Widen the options before committing - framed options compared on stated criteria, ending in a…
Run a SpecWeave increment unattended until every task is done, then verify and close. Use for "auto mode", "run until done", "ship this while I sleep".
$ npx -y skills add anton-abyzov/specweave --skill auto --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/autoContext preview
The summary Claude sees to decide when to auto-load this skill.
Run a SpecWeave increment unattended until every task is done, then verify and close. Use for "auto mode", "run until done", "ship this while I sleep".
description: Run a SpecWeave increment unattended until every task is done, then verify and close. Use for "auto mode", "run until done", "ship this while I sleep". argument-hint: "[increment-ids...] [--dry-run|--reset]" version: 3.0.0
<!-- Generated from skills/sw-auto/SKILL.md by scripts/build/generate-skills.mjs. Edit the source, then npm run build. -->
Auto mode is the sw-do loop without stopping to ask. The bar does not drop: claim before editing, a passing test for every `done`, verify before closing.
1. The spec has no open questions and every task has `Files` and a `Test`. If not, fix the spec first. 2. `specweave auto 0042` records the session (`--dry-run` previews it, `--reset` clears stale state). In a tool that runs SpecWeave's Stop hook (Claude Code with the `sw` plugin) the hook hands you the remaining work after every turn until nothing is left. In any other tool, nothing feeds you back: keep looping yourself. 3. `specweave auto-status` shows progress; `specweave cancel-auto` stops it.
1. `specweave task next` → `specweave task claim T-NN` → implement inside its `Files` → commit `0042: ...` → `specweave task done T-NN --run "<Test>"`. 2. A failing test is fixed in the next turn, never marked done. 3. Genuinely blocked (missing secret, ambiguous spec, external dependency): `specweave task block T-NN --reason "<what is missing>"` and move on. Blocked tasks still count as work left: when only blocked tasks remain, run `specweave cancel-auto` and tell the user what each one needs, instead of looping until the turn limit. 4. Nothing claimable left: run sw-done (verify, review, complete).
Before the session ends for tokens or time: `specweave handoff --reason "auto: out of tokens"`. The next session, in any tool or account, says "pick up" and continues.
Without the CLI there is no hook and no session file: follow the manual path of sw-do in a loop until every task in spec.md has a `done` or `skip` line, then sw-done.
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
Widen the options before committing - framed options compared on stated criteria, ending in a…
Work a SpecWeave increment task by task - claim, implement inside the task's Files, test,…
Close a SpecWeave increment - every task done or skipped, specweave verify green, a…
Hand work to another tool, account or machine and pick it up there, in two words. Use when…
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach…
Delegate closed-set decisions to Jev (TypeSafe System One) instead of a frontier turn —…