austinmao

goal-wrap

Bundle current work into a self-contained autonomous-execution prompt with tracked done-when criteria, best-effort architecture grounding, and full autonomy by default (pass --gates to enable operator confirmation prompts).

plan-decompose

Create and decompose a lightweight plan with opposite-first review, one bounded read-only active-host fallback, and bounded self-repair; returns success or an evidence-backed terminal block.

swarm

Ad-hoc parallel task executor. Pass natural language tasks directly (or --tasks-file); independent tasks use concurrent host-native volume/execution/judgment roles and dependent tasks run serially. No spec directory required; use feature-implement for full-feature work.

adopt-wip

Salvage coherent uncommitted work left in a stalled worktree or abandoned agent session. Use when resuming a run, when a parallel worktree contains valuable WIP, or when deciding whether to adopt, finish, and ship existing work instead of rebuilding from scratch.

autonomy-grant

Pre-approve the operator gates an unattended run will hit — prod push, deploy, merge, DNS — so the run proceeds through them without stopping. Use at plan approval, while the operator is present, to build the typed approval ledger that /feature-implement --autonomous checks mechanically.

code-uplift

Review + refactor code that's already written — same gsd machinery as feature-spec/feature-implement but findings-driven instead of spec-driven. Adversarial cross-model review, refactor phases, test uplift to the coverage floor, smoke/e2e via canary-gate, review-gate finish tail.

continue-compact

Prepare a durable handoff and a host-native resume command before the built-in compact operation. Use when context is low or the user asks to continue after compaction.

feature-implement

Execute a decomposed feature via the gsd-core loop with preflight-only host fallback, no stateful cross-vendor replay, autonomy grants, gates.py completion authority, and a fail-closed review/ship tail. --adhoc uses the same walls over gsd-quick.

feature-spec

Spec-first pipeline: speckit.specify → speckit.plan → speckit.clarify → spec-decompose (swarm) → preflight (default) → autonomy-grant (MAX-AUTH auto-grant default; --gated to review). Produces spec.md + plan.md + tasks.md + a proven preflight + a grant ledger, ready for /feature-implement NNN --autonomous.

feature

DEPRECATED (v3.19.0) — replaced by /feature-spec (spec→plan→tasks→preflight→grant) + /feature-implement --autonomous (swarm impl→QA→review-gate→ship→canary). This stub chains the replacements for back-compat and will be removed next release.

fix

Investigate a bug (root cause, not symptom), then fix it through host-native /feature-implement --adhoc; only review gates cross to the opposite model family.

git-branch-cleanup

Triage branches against the base branch, merge only CI-green non-gated ones, prune merged refs + worktrees. Squash-merge + operator-gate aware.

git-branch-consolidate

Audit every git worktree and branch for spec/plan/test completeness, then plan the consolidation down to one origin/main. Use for 'audit all worktrees', 'what's unmerged', 'consolidate branches', 'get everything to main', 'branch estate'.

preflight

Prove every env var, secret, and service the run will need is present and reachable BEFORE starting an unattended or overnight run. Use at the planning stage — after decompose, before /feature-implement — so the run never stalls at 3am on a missing variable or dead endpoint.

Code & Development Listed

review-gate

Host-neutral pre-merge review gate. Tries the opposite CLI first, allows one explicit read-only active-host fallback, and fails closed when mandatory review evidence is unavailable. Blocks shipping on HIGH/CRITICAL findings.

spec-decompose

Decompose an approved feature spec into an executable gsd-core phase plan: seed .planning/{PROJECT,REQUIREMENTS,ROADMAP}.md from specs/NNN/{spec,plan}.md, then drive /gsd-plan-phase (research → wave-parallel plans → plan-checker). Replaces the ruflo specialist-swarm tasks.md decomposition (v2.0.0, spec 002).

spec-status

Status check for the current spec run: what's done, running, tested, blocked, and next. Fan out volume, execution, and judgment roles over git, .planning, gates, runner state, evidence, and hygiene; write a status report and host-native handoff.

task-swarm

Lightweight autonomous feature pipeline: self-healing plan-decompose → preflight → autonomy-grant → feature-implement --autonomous. DRY sequencing only; child skills own all machinery.

Testing & QA Listed

testing-policy

Canonical FFS testing doctrine — mock-minimization ladder, real-browser verification, console/network tripwires, independent test authorship, BDD-as-executable-input, coverage floor, smoke design. Other skills reference this instead of restating it.

Code & Development Listed

verify-review

Verify a code review before acting on it. Use when Claude, Codex, review-gate, or a human reviewer returns a verdict (PASS, FIX_FIRST, REQUEST_CHANGES, CRITICAL finding) and you must decide whether to merge, fix, or push back — spot-check the load-bearing claims against current HEAD first.

ffs-init

Umbrella FFS initialization: install repo-scoped dependencies (Phase 0), then build or refresh the environment registry (config/environments.yaml) — propose rows from repo evidence, review them in one batched session, apply atomically, validate, update in place. Never leaks a secret VALUE (names only) and never re-asks a declined proposal.

area-status

Area health check: is a named area of the codebase actually done, evidenced, and safe to call green — not just described as done. Fan out volume, execution, and judgment roles over deterministic facts, evidence age, and post-evidence commit drift; write a graded, ref-pinned report. `--live` gates any outward probe behind a typed check-grant.

land-queue

Serially land finished branches: collect from takeover records, estate discovery, and explicit args; rebase, implement, review, watch CI, merge under exact grant, finalize, and journal every step. v1 is strictly serial.

retro-triage

Render guarded, injection-safe maintainer briefs from validated FFS retro issue metadata.

spec-guide

Create role-based instructions for a feature delivered by a spec, split into developer, admin, and user guidance, then verify every numbered step through its real delivery vehicle. Use after or near spec completion when someone asks how to configure, operate, or use the feature and needs browser, API/MCP, Telegram, email, CLI, webhook, worker, or design evidence rather than untested prose.