Menu
Mark an item blocked and inject the standard
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-blocked |
| description | Mark an item blocked and inject the standard |
| argument-hint | <ITEM-ID> |
| allowed-tools | ["Bash","Edit"] |
| paths | [".squad/items/**"] |
| disable-model-invocation | true |
You are marking item $ARGS as blocked. Run:
squad blocked $ARGS --reason "<one-line reason>"
Then add a ## Blocker section to the item file (.squad/items/$ARGS-*.md) using this template:
## Blocker
**What blocks:** <concrete description of what is preventing progress>
**What is needed to unblock:** <specific action, decision, dependency, or external answer>
**Who/what could unblock:** <agent, user, external party, or "waiting on <event>">
Then: