Menú
Tick the squad team — surface mentions and file conflicts. Address mentions BEFORE continuing other work.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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.
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.
Evidence-gated close-out for an item. Requires test output paste, code review, and quality-bar pass before squad done runs.
| name | squad-tick |
| description | Tick the squad team — surface mentions and file conflicts. Address mentions BEFORE continuing other work. |
| argument-hint | |
| allowed-tools | ["Bash"] |
| paths | [".squad/**"] |
| disable-model-invocation | true |
Run:
squad tick
Read the output carefully. If there are unread mentions, address them BEFORE continuing whatever you were doing. A missed heads-up can waste the next hour.
For each mention:
squad ask @<sender> or squad say --to <thread>.fyi: acknowledge briefly if action is needed, otherwise note and continue.If tick reports stale claims (yours), heartbeat them or release them depending on whether you are still working on them.