select
Select
Intent
Pick a task source, refine it into dependency-aware atomic tasks, schedule parallel waves when safe, and emit an orchestration plan.
This skill is plan-only:
- It does not implement changes (no code edits; no running workers).
- It does not mutate the task source (no
SLICES.mdwrites, noplan-N.mdwrites); instead it emits explicit manual writeback steps when needed (e.g., "mark as in_progress"). - It is orchestration-agnostic: the output is a neutral plan schema (not tied to a specific executor).
It may also emit a small pipeline for driving planning artifacts into execution (manual steps; optionally loopable).
Swarm-ready planning
$select is optimized for parallel multi-agent execution, so it prefers plans that are explicit, decomposed, and lock-safe.
- Explore the codebase (read-only) when needed to ground tasks in real paths/components and to set tight
scopelocks. - Ask clarifying questions when multiple reasonable approaches exist; include a recommended default.
- Atomic tasks: each task should be independently executable by a single worker.
- Workstream shaping: identify major workstreams first, then map atomic tasks into those workstreams.
More from tkersey/dotfiles
grill-me
>
100complexity-mitigator
Mitigate incidental complexity in existing code when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, dominant-risk triage, ranked simplification steps, one visibility artifact, and a TRACE assessment. Do not use for greenfield requirements discovery, architecture selection, or delivery planning.
59creative-problem-solver
Lateral-thinking playbook that always returns a five-tier strategy portfolio (Quick Win through Moonshot). Use when you need options, alternatives, or trade-offs; when progress is stalled or failing repeatedly; or when you ask to think creatively, reframe constraints, and choose a strategic path before execution.
59mesh
Use `$mesh` for homogeneous leaf-batch execution over `spawn_agents_on_csv`: once planning has shaped repeated independent units, prefer one substantive row per unit with structured results and explicit concurrency.
47web-browser
Use when tasks need real-browser web automation in Chrome/Chromium via CDP: open or navigate URLs, click/type/select in forms, run page JS, wait for selectors, scrape structured content, capture screenshots, validate UI flows, or run measured web-browser latency checks (`bench:eval`, `bench:all`) for perf regressions.
43invariant-ace
Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another implementation workflow with invariant checks first.
31