AGENT SKILL

sweep

Fan a mechanical or partitionable job out to parallel workers, one complete brief per slice, and aggregate one evidenced report. Use for renames across many files, per-package migration batches, applying a codemod in slices, or parallel probes.

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
sweep
metadata
{ "layer": "L3", "source": "cursor/plugins@1e5c90a:pstack/skills/swarm/SKILL.md", "license": "MIT" }
description
Fan a mechanical or partitionable job out to parallel workers, one complete brief per slice, and aggregate one evidenced report. Use for renames across many files, per-package migration batches, applying a codemod in slices, or parallel probes.

03 SKILL.md 正文

Sweep

Split a job into slices, give each slice to a worker (delegate) with a brief that leaves nothing to decide, and return one report. Open a task list with one entry per phase below before spawning anything.

1. Frame

  1. Done predicate. State what must be true when the sweep is finished, and what the report returns.
  2. Lever first. Apply build-the-lever. If one script or codemod can do every slice the same way, do the first unit by hand, build the script, prove it on that unit by diffing against your hand-done version, and run it yourself. Fan out only what a script can't do in one pass, or the per-slice checking of what it did.
  3. Shape.
    • Partition: one slice per package, directory or file batch. File sets are disjoint: two workers never write the same file.
    • Race: N workers on the same brief. Declare the selection rule before spawning: first pass, rank all, or best of.
  4. N comes from the user or the shape. Each worker that writes gets its own files; each that measures gets the exact commit SHAs and the method.

2. Brief

Every brief stands alone. It names:

  • the goal and the slice: inputs and the exact files the worker may touch;
  • the recipe, or the lever command to run, and the do-not-touch fences;
  • the expected output shape;
  • the check command, from the profile: ven-profile run commands.test.single --file <path>, ven-profile run commands.typecheck, or the lever's own check;
  • the verdict to report: PASS, ISSUES (every issue it can prove, each with evidence, not just the first) or BLOCKED (one question). ISSUES is for probe and check slices; an edit slice whose check fails is fixed within its scope or reported BLOCKED.

A brief that contains "decide" or "figure out" is not ready. Make the decision first, or ask the user.

3. Fan out

Hand off every slice at once, as delegate describes, in the background where your agent allows it. If a worker drops out, continue with the rest and note it.

4. Aggregate

  • Read each final result. Drop one that lacks a verdict, lacks the check's exit code, or touched files outside its slice, and respawn that worker once with the same brief plus what was missing. A second miss is a gap. A gap is never a pass.
  • BLOCKED: answer the question (ask the user if it is their decision) and respawn with the answer in the brief.
  • Coverage needs a result for every slice. A race applies the rule declared up front.
  • A worker's PASS is a claim. Check the combined diff yourself (git diff --stat against the slice list) and apply prove-it-works.
  • Run verify on the combined tree.

5. Report

One report in chat, no raw worker output:

Slice Verdict Evidence
<slice> PASS / ISSUES / BLOCKED / gap <check command> exit <code>

Then one line per issue, the gaps and dropouts, and the race rule if one was used.

Record: ven-decisions add --step sweep --decision "<n> slices: <p> pass, <i> issues, <g> gaps" --evidence "<combined check> exit <code>".

04 同仓库更多 Skills

Ventorius
Ventorius/ven-stack

yeet

Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.

★ 0
Ventorius
Ventorius/ven-stack

write-docs

Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.

★ 0
Ventorius
Ventorius/ven-stack

why

Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.

★ 0
Ventorius
Ventorius/ven-stack

verify

Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.

★ 0
Ventorius
Ventorius/ven-stack

unslop

Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.

★ 0
Ventorius
Ventorius/ven-stack

type-discipline

Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.

★ 0