メニュー
End-of-session 3-bullet brief plus claim release. Invokes the squad-handoff skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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-handoff-cmd |
| description | End-of-session 3-bullet brief plus claim release. Invokes the squad-handoff skill. |
| argument-hint | |
| allowed-tools | ["Bash","Edit"] |
| paths | [".squad/**"] |
| disable-model-invocation | true |
You are wrapping up the session. Invoke the squad-handoff skill, then post the 3-bullet brief:
in_progress or review and where it stands. If clear, say "queue clear."If you are pausing mid-item:
## Session log entry to the item file with what you did, what is left, gotchas, and the next concrete step.squad say "end of session, picking up <next step> tomorrow".If you are truly handing off to another agent:
squad release $ARGS --outcome released
And name the next concrete step in the release message.
After posting the brief, sign off.