close-all
Batch Close All Complete Increments
Closes all active increments that have reached 100% task completion by delegating each one to sw:done. This skill is a thin batch-discovery loop; all actual closure logic (gates, reports, sync) lives in sw:done.
Step 1: Discover Closeable Increments
for meta in $(find .specweave/increments -maxdepth 2 -name "metadata.json" | sort); do
st=$(jq -r '.status' "$meta" 2>/dev/null)
[ "$st" != "active" ] && [ "$st" != "in-progress" ] && [ "$st" != "ready_for_review" ] && continue
d=$(dirname "$meta"); id=$(basename "$d"); tasks="$d/tasks.md"
[ ! -f "$tasks" ] && continue
pending=$(grep -c '\[ \]' "$tasks" 2>/dev/null || echo 0)
done_count=$(grep -c '\[x\]' "$tasks" 2>/dev/null || echo 0)
if [ "$pending" -eq 0 ] && [ "$done_count" -gt 0 ]; then
echo "CLOSEABLE: $id"
fi
done
If no closeable increments are found, report "No increments ready for closure" and stop.
Step 2: Dry-run
If the user passed --dry-run, print the discovered list and stop without closing anything.
Step 3: Delegate each to sw:done
Iterate the discovered list sequentially. For each <ID>:
Skill({ skill: "sw:done", args: "<ID>" })
sw:done owns the actual closure workflow: code-review, simplify, grill, judge-llm, PM validation, external sync, and final status transition. Close sequentially to respect dependency order; if sw:done fails for an increment, log the failure and continue with the next.
Step 4: Summary
Print a final summary with CLOSED / FAILED counts per increment. Failures are not retried here — the user re-runs sw:done <ID> individually once blockers are resolved.
Notes
- All gate logic lives in
sw:done. This skill MUST NOT duplicate closure behaviour. - Parallel closure is intentionally not supported — race conditions on shared living docs are a real hazard.
More from anton-abyzov/specweave
technical-writing
Technical writing expert for API documentation, README files, tutorials, changelog management, and developer documentation. Covers style guides, information architecture, versioning docs, OpenAPI/Swagger, and documentation-as-code. Activates for technical writing, API docs, README, changelog, tutorial writing, documentation, technical communication, style guide, OpenAPI, Swagger, developer docs.
45spec-driven-brainstorming
Spec-driven brainstorming and product discovery expert. Helps teams ideate features, break down epics, conduct story mapping sessions, prioritize using MoSCoW/RICE/Kano, and validate ideas with lean startup methods. Activates for brainstorming, product discovery, story mapping, feature ideation, prioritization, MoSCoW, RICE, Kano model, lean startup, MVP definition, product backlog, feature breakdown.
43kafka-architecture
Apache Kafka architecture expert for cluster design, capacity planning, and high availability. Use when designing Kafka clusters, choosing partition strategies, or sizing brokers for production workloads.
34docusaurus
Docusaurus 3.x documentation framework - MDX authoring, theming, versioning, i18n. Use for documentation sites or spec-weave.com.
29frontend
Expert frontend developer for React, Vue, Angular, and modern JavaScript/TypeScript. Use when creating components, implementing hooks, handling state management, or building responsive web interfaces. Covers React 18+ features, custom hooks, form handling, and accessibility best practices.
29reflect
Self-improving AI memory system that persists learnings across sessions in CLAUDE.md. Use when capturing corrections, remembering user preferences, or extracting patterns from successful implementations. Enables continual learning without starting from zero each conversation.
27