User input: $ARGUMENTS
- The ticket key (e.g. RND-123) is in there; take it from that input
--hitlpresent → pass it tosquad:tkt-ship. Default: fully autonomous- Anything else = extra instructions; apply them throughout the run
Config
Before anything else: read ${CLAUDE_SKILL_DIR}/../squad-config.md
Squad
If the /herdr skill is available, run it. You are the orchestrator/delegator/supervisor — you do not implement, you only delegate with the following instructions.
You may choose how many sessions are in the squad. The minimum is 2 workers:
- Implementor — steps 3–4
- QA/Code Reviewer — the reviewer in step 5. Rejected → back to the Implementor.
No herdr → you are the Implementor, and QA/Code Reviewer is a fresh subagent.
Flow
Run every step, in order. Never skip one.
STEP 1 Gather TKT Context
Invoke the squad:tkt-context skill with the ticket key as args.
STEP 2 Identify the TKT
- Tkt must be assigned to me — if not, stop and report
- Bug or feature?
reopen? → read QA's comment and the previous PR first- Move to
In Progress, create the worktree
STEP 3 Work
Invoke the squad:tkt-work skill with the ticket key (+ extra instructions) as args.
STEP 4 Prove
Invoke the squad:tkt-evidence skill with the ticket key as args.
STEP 5 Ship
Invoke the squad:tkt-ship skill with the ticket key (+ --hitl if given) as args.