Menü
Atomically claim an item by ID. Verifies references, applies RED-first if AC names concrete failures.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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-pick |
| description | Atomically claim an item by ID. Verifies references, applies RED-first if AC names concrete failures. |
| argument-hint | <ITEM-ID> |
| allowed-tools | ["Bash","Read"] |
| paths | [".squad/items/**"] |
| disable-model-invocation | true |
You are claiming item $ARGS. Run:
squad claim $ARGS --intent "<one sentence describing what you intend to ship>"
If the command exits non-zero, the item is already claimed by someone else — pick another and tell the user.
If the claim succeeds:
.squad/items/$ARGS-*.md). The ## Acceptance criteria section is the contract.file:line reference in the item body against current code. Items rot — line numbers shift, files get renamed, constants change. Open each reference and confirm the described condition is still true. If the item is stale, correct the body before starting.squad-premise-validation and write the RED test FIRST against current code. If the test passes unmodified, the bug does not reproduce — stop and reclassify per the skill.squad-loop and proceed with TDD.Announce the claim in one line: "Claimed $ARGS: . Starting with <plan>."