Menu
Onboard or resume in one step — squad go does init/register/claim/AC/mailbox.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Every "tests pass" / "build green" / "feature works" claim needs the actual command output pasted into the conversation. Bare assertions are worth zero.
The operating loop every session follows — register, tick, pick, work, checkpoint, test, review, commit, close. Use whenever you start or resume work on a squad-managed repo.
Post often, post small, post honestly. The team needs visibility into your non-obvious state — not a change log. Use the typed verbs (thinking / milestone / stuck / fyi / ask) so peers can route attention.
Tick the squad team — surface mentions and file conflicts. Address mentions BEFORE continuing other work.
Before signing off — whether you finished an item or stopped mid-flight — post a 3-bullet summary. Shipped, in flight / queued, surprised by. Three bullets, no ceremony.
Run a structured intake interview with the user — open a session, ask one focused question per turn, draft the bundle, confirm with the user, then commit. Supports green-field (mode=new) and refine-mode (mode=refine) flows.
| name | squad-work |
| description | Onboard or resume in one step — squad go does init/register/claim/AC/mailbox. |
| argument-hint | |
| allowed-tools | ["Bash","Read"] |
| paths | [".squad/**"] |
| disable-model-invocation | true |
You are starting (or resuming) work on a squad-managed repo. Run the orchestrator:
squad go
squad go is idempotent. It will:
squad init --yes if .squad/ is absent.If a claim is already held by your agent, squad go resumes it — re-prints AC and re-flushes mailbox.
After the command returns:
squad-loop skill and proceed from step 4 (work the item) onward.If the output says no ready items, ask the user what they want done; then file an item and re-run squad go.