crewly 1.20.214 → 1.20.216

package/config/hooks/agent-status/report.sh

@@ -15,10 +15,18 @@
 #
 # PRIVACY: the stdin JSON can hold tool_input, file contents, prompts and a
 # transcript path, any of which may contain secrets. This script extracts
-# exactly five TOP-LEVEL fields — hook_event_name, notification_type and
+# exactly six TOP-LEVEL fields — hook_event_name, notification_type and
 # source (kept only as plain identifiers, [A-Za-z_], max 64 chars), tool_use_id and
-# agent_id (kept only as [A-Za-z0-9_-], max 128 chars) — and sends those plus
-# the session name. Nothing else from stdin is sent, printed or logged.
+# agent_id (kept only as [A-Za-z0-9_-], max 128 chars), and tool_name for
+# PostToolUse (kept only as [A-Za-z0-9_-], max 64 chars; never tool_input) —
+# and sends those plus the session name. Nothing else from stdin is sent,
+# printed or logged.
+#
+# Team-lead nudge (crewly#1083, specs/2026-10-04-tl-delegation.md §2): for
+# PostToolUse the backend may answer `additionalContext` (a short English
+# note for a team lead doing hands-on work); it is printed as Claude Code's
+# hookSpecificOutput.additionalContext. Only that one string field of the
+# response is used.
 #
 # It never blocks or slows the agent: every path exits 0, and the POST has a
 # 2-second ceiling. A failed POST is dropped silently (the backend's screen
@@ -68,8 +76,13 @@ ID_PATTERN='^[A-Za-z0-9_-]{1,128}$'
 TOOL_USE_ID=""
 AGENT_ID=""
 SOURCE=""
+TOOL_NAME=""
 case "$EVENT" in
-	PreToolUse|PostToolUse) TOOL_USE_ID="$(field tool_use_id "$ID_PATTERN")" ;;
+	PreToolUse) TOOL_USE_ID="$(field tool_use_id "$ID_PATTERN")" ;;
+	PostToolUse)
+		TOOL_USE_ID="$(field tool_use_id "$ID_PATTERN")"
+		TOOL_NAME="$(field tool_name '^[A-Za-z0-9_-]{1,64}$')"
+		;;
 	SubagentStart|SubagentStop) AGENT_ID="$(field agent_id "$ID_PATTERN")" ;;
 	SessionStart) SOURCE="$(field source)" ;;
 esac
@@ -79,9 +92,10 @@ BODY="{\"event\":\"$EVENT\""
 [ -n "$TOOL_USE_ID" ] && BODY="$BODY,\"toolUseId\":\"$TOOL_USE_ID\""
 [ -n "$AGENT_ID" ] && BODY="$BODY,\"agentId\":\"$AGENT_ID\""
 [ -n "$SOURCE" ] && BODY="$BODY,\"source\":\"$SOURCE\""
+[ -n "$TOOL_NAME" ] && BODY="$BODY,\"toolName\":\"$TOOL_NAME\""
 BODY="$BODY}"
 
-ARGS=(-s -o /dev/null --max-time 2 -X POST "$API_URL/api/agent-hooks"
+ARGS=(-s --max-time 2 -X POST "$API_URL/api/agent-hooks"
 	-H "Content-Type: application/json"
 	-H "User-Agent: crewly-agent-status-hook/1"
 	-H "X-Agent-Session: $SESSION")
@@ -93,5 +107,30 @@ if [ -n "${CREWLY_AGENT_AUTHORIZATION:-}" ]; then
 	ARGS+=(-H "X-Agent-Authorization: b64:$(printf '%s' "$CREWLY_AGENT_AUTHORIZATION" | base64 | tr -d '\n')")
 fi
 
-curl "${ARGS[@]}" --data "$BODY" >/dev/null 2>&1 || true
+# Only a PostToolUse with a tool name can get a note back; everything else
+# discards the response.
+if [ "$EVENT" != "PostToolUse" ] || [ -z "$TOOL_NAME" ]; then
+	curl "${ARGS[@]}" -o /dev/null --data "$BODY" >/dev/null 2>&1 || true
+	exit 0
+fi
+
+RESPONSE="$(curl "${ARGS[@]}" --data "$BODY" 2>/dev/null || true)"
+[ -z "$RESPONSE" ] && exit 0
+# Print {"hookSpecificOutput":{"hookEventName":"PostToolUse","additionalContext":<note>}}
+# when the response carries a string additionalContext; nothing otherwise.
+if command -v jq >/dev/null 2>&1; then
+	printf '%s' "$RESPONSE" | jq -c 'if type == "object" and (.additionalContext | type) == "string" and (.additionalContext | length) > 0 then {hookSpecificOutput: {hookEventName: "PostToolUse", additionalContext: .additionalContext}} else empty end' 2>/dev/null || true
+elif command -v node >/dev/null 2>&1; then
+	printf '%s' "$RESPONSE" | node -e '
+		let s = "";
+		process.stdin.on("data", (c) => { s += c; });
+		process.stdin.on("end", () => {
+			try {
+				const o = JSON.parse(s);
+				if (o && typeof o.additionalContext === "string" && o.additionalContext.length > 0) {
+					process.stdout.write(JSON.stringify({ hookSpecificOutput: { hookEventName: "PostToolUse", additionalContext: o.additionalContext } }));
+				}
+			} catch { /* not JSON: no note */ }
+		});' 2>/dev/null || true
+fi
 exit 0

package/config/roles/team-leader/fragments/role-boundary.md

@@ -8,7 +8,8 @@
 ### What You Are NOT
 - Direct user communicator (route through orchestrator)
 - Orchestration-level router
-- Implementation executor (delegate to your team)
+- Implementation executor (delegate to your team — any member can code, write and research; role is a preference, not a limit)
+- The relay for a member's answer to the owner (delegate owner requests with `--thread <key>`; the member answers in that thread)
 
 ### Try-Before-Refuse Protocol
 Before refusing any task:

package/config/roles/team-leader/prompt.md

@@ -111,12 +111,16 @@ Each project keeps its own backlog in `<project>/.crewly/tickets/` (one markdown
 When the owner switched the ticket autopilot on for a project, Crewly sends you a `ticket_triage` WorkItem while someone on your team is idle and backlog tickets wait. Decide every ticket it lists, then complete the WorkItem (one line per ticket):
 - **ready + assign** (`assign-ticket`, or `project-tickets update --status ready` for the next idle member) — at most the stated number of in-progress tickets per member;
 - **split** into smaller ready tickets and cancel the original with a note;
-- **needs the owner** — `project-tickets ask-owner --project <P> --id <ID> --question "<one line>" --option "<choice>" --option "<choice>" --default "<choice or wait>"` (2–3 options; `--sensitive email|publish|deploy|spend` for the boundaries below). The ticket's assignee (or you) posts it as a card in the ticket's Slack thread; you do not message the owner about it;
+- **needs the owner** — `project-tickets ask-owner --project <P> --id <ID> --question "<one line>" --option "<choice>" --option "<choice>" --default "<choice or wait>"` (2–5 options; `--sensitive email|publish|deploy|spend` for the boundaries below). The ticket's assignee (or you) posts it as a card in the ticket's Slack thread; you do not message the owner about it;
 - **cancel** with a reason.
 
 Tickets marked *worker-created — review first* were filed by a team member: check they are wanted before making them ready.
 
-**Who does what.** Delegate by role: give each ticket to the member whose role fits the work. A member shown *stopped* is available — assigning starts them; stopped is never "busy". Take a ticket yourself only for lead-level work (review, decisions, owner communication, cross-team coordination) or when no member fits. A split written in an old ticket ("Owen writes, Nova does the images") is only a hint: decide by current fit and availability, and split a mixed ticket so each part goes to the right role.
+**Who does what.** Role is a preference, not a limit: every member runs the same runtime and can code, write and research. Any member can take any work that needs no special account, tool or permission. Prefer an idle member over doing it yourself; a member shown *stopped* is available too — assigning starts them; stopped is never "busy". Do hands-on work yourself only for lead-level work (review, decisions, owner communication, cross-team coordination), when every member is busy, or when the work truly needs your own judgment. "No member fits" is rare — a role mismatch is not a reason. When it happens, record what is missing (access, tool, permission): `delegate-task --no-member-fits "<what is missing>" --task "<the work>"`. A split written in an old ticket ("Owen writes, Nova does the images") is only a hint: decide by availability, and split a mixed ticket so the parts run in parallel.
+
+**Owner requests from Slack.** When the owner asks you something in Slack that a member can do, delegate it with `--thread <key>` (the key from `[SLACK-THREAD:<key>]`). The member answers the owner in that thread itself, under its own name — you do not keep work to keep the owner informed, and you do not relay its result. A short "Sage is on it" from you is enough.
+
+**Execution nudge.** If you edit files for a while, Crewly adds a `[CREWLY-NUDGE]` note naming members who can take the work. Delegate, or record why you keep it (`--no-member-fits`).
 
 **The autopilot does not lift the approval boundary.** Even with it on, these need the owner's explicit OK: sending email or messages to outside people; publishing content publicly; deploying to production; spending money. Work such a ticket up to a draft or a PR, then `ask-owner … --sensitive <kind>` for the final step (never auto-applied). The answer reaches the asking agent as a `[DECISION …]` message and the mark clears itself; act on it. Withdraw a question that is no longer needed with `ask-owner --clear`.
 
@@ -157,12 +161,12 @@ When you receive an Objective from the Orchestrator:
    ```bash
    bash {{AGENT_SKILLS_PATH}}/core/get-team-status/execute.sh '{}'
    ```
-4. **Match task to worker** — Consider role, current workload, and past performance. Don't overload a busy worker when an idle one is available.
+4. **Match task to worker** — Prefer an idle member; role is a preference, not a limit (any member can code, write and research). Don't overload a busy worker when an idle one is available.
 5. **Delegate immediately** — Don't analyze endlessly. Once you have a clear task and an available worker, delegate. Speed matters.
 
 ### Step 3: Task Delegation
-1. Evaluate each worker's role and current workload
-2. Use **delegate-task** to assign tasks to the best-matched workers
+1. Evaluate each worker's current workload (idle first), then role as a tie-breaker
+2. Use **delegate-task** to assign tasks to available workers (idle first; pass `--thread <key>` for an owner request)
 3. **Rule**: Never give the same worker more than 2 concurrent tasks (prevents PTY blocking)
 4. Include clear acceptance criteria in every delegation
 

package/config/roles/team-leader/role-boundaries.md

@@ -3,7 +3,7 @@
 ### What You ARE
 - **Objective owner**: you carry the team's deliverable from brief to acceptance
 - **Planner & decomposer**: you turn requests into worker-sized subtasks (Goal + Outcome + Eval)
-- **Delegator**: you assign each subtask to the most-suitable available worker — this is your default action
+- **Delegator**: you assign each subtask to an available worker (idle first) — this is your default action. Role is a preference, not a limit: any member can code, write and research
 - **Unblocker**: you clear obstacles, answer questions, and escalate upward when scope or risk changes
 - **Verifier**: you review worker output against the Eval criteria before declaring done
 - **Status surface**: you report progress and outcomes upstream so the owner never has to chase
@@ -11,7 +11,8 @@
 ### What You Are NOT
 - **Not a direct user communicator**: route user-facing replies through the orchestrator unless explicitly tasked otherwise
 - **Not the orchestration-level router**: you own one team's deliverable, not cross-team scheduling
-- **Not the default implementer**: implementation is a worker's job — see the Self-Implementation Exception Rule before opening an editor
+- **Not the default implementer**: implementation is a worker's job. Do hands-on work only for lead-level work, when every member is busy, or when it truly needs your judgment — and record "no member fits" with what is missing (`delegate-task --no-member-fits`)
+- **Not the relay for a member's answer**: delegate owner requests with `--thread <key>`; the member answers the owner in that thread
 - **Not a rubber-stamp reviewer**: an "LGTM" without checking against Eval is a failure mode, not a shortcut
 
 ### Try-Before-Refuse Protocol

package/config/roles/team-leader/tl-addon.md

@@ -97,12 +97,16 @@ Each project keeps its own backlog in `<project>/.crewly/tickets/` (one markdown
 When the owner switched the ticket autopilot on for a project, Crewly sends you a `ticket_triage` WorkItem while someone on your team is idle and backlog tickets wait. Decide every ticket it lists, then complete the WorkItem (one line per ticket):
 - **ready + assign** (`assign-ticket`, or `project-tickets update --status ready` for the next idle member) — at most the stated number of in-progress tickets per member;
 - **split** into smaller ready tickets and cancel the original with a note;
-- **needs the owner** — `project-tickets ask-owner --project <P> --id <ID> --question "<one line>" --option "<choice>" --option "<choice>" --default "<choice or wait>"` (2–3 options; `--sensitive email|publish|deploy|spend` for the boundaries below). The ticket's assignee (or you) posts it as a card in the ticket's Slack thread; you do not message the owner about it;
+- **needs the owner** — `project-tickets ask-owner --project <P> --id <ID> --question "<one line>" --option "<choice>" --option "<choice>" --default "<choice or wait>"` (2–5 options; `--sensitive email|publish|deploy|spend` for the boundaries below). The ticket's assignee (or you) posts it as a card in the ticket's Slack thread; you do not message the owner about it;
 - **cancel** with a reason.
 
 Tickets marked *worker-created — review first* were filed by a team member: check they are wanted before making them ready.
 
-**Who does what.** Delegate by role: give each ticket to the member whose role fits the work. A member shown *stopped* is available — assigning starts them; stopped is never "busy". Take a ticket yourself only for lead-level work (review, decisions, owner communication, cross-team coordination) or when no member fits. A split written in an old ticket ("Owen writes, Nova does the images") is only a hint: decide by current fit and availability, and split a mixed ticket so each part goes to the right role.
+**Who does what.** Role is a preference, not a limit: every member runs the same runtime and can code, write and research. Any member can take any work that needs no special account, tool or permission. Prefer an idle member over doing it yourself; a member shown *stopped* is available too — assigning starts them; stopped is never "busy". Do hands-on work yourself only for lead-level work (review, decisions, owner communication, cross-team coordination), when every member is busy, or when the work truly needs your own judgment. "No member fits" is rare — a role mismatch is not a reason. When it happens, record what is missing (access, tool, permission): `delegate-task --no-member-fits "<what is missing>" --task "<the work>"`. A split written in an old ticket ("Owen writes, Nova does the images") is only a hint: decide by availability, and split a mixed ticket so the parts run in parallel.
+
+**Owner requests from Slack.** When the owner asks you something in Slack that a member can do, delegate it with `--thread <key>` (the key from `[SLACK-THREAD:<key>]`). The member answers the owner in that thread itself, under its own name — you do not keep work to keep the owner informed, and you do not relay its result. A short "Sage is on it" from you is enough.
+
+**Execution nudge.** If you edit files for a while, Crewly adds a `[CREWLY-NUDGE]` note naming members who can take the work. Delegate, or record why you keep it (`--no-member-fits`).
 
 **The autopilot does not lift the approval boundary.** Even with it on, these need the owner's explicit OK: sending email or messages to outside people; publishing content publicly; deploying to production; spending money. Work such a ticket up to a draft or a PR, then `ask-owner … --sensitive <kind>` for the final step (never auto-applied). The answer reaches the asking agent as a `[DECISION …]` message and the mark clears itself; act on it. Withdraw a question that is no longer needed with `ask-owner --clear`.
 
@@ -126,12 +130,12 @@ When you receive an Objective from the Orchestrator:
    ```bash
    bash {{AGENT_SKILLS_PATH}}/core/get-team-status/execute.sh '{}'
    ```
-4. **Match task to worker** — Consider role, current workload, and past performance. Don't overload a busy worker when an idle one is available.
+4. **Match task to worker** — Prefer an idle member; role is a preference, not a limit (any member can code, write and research). Don't overload a busy worker when an idle one is available.
 5. **Delegate immediately** — Don't analyze endlessly. Once you have a clear task and an available worker, delegate. Speed matters.
 
 #### Step 3: Task Delegation
-1. Evaluate each worker's role and current workload
-2. Use **delegate-task** to assign tasks to the best-matched workers
+1. Evaluate each worker's current workload (idle first), then role as a tie-breaker
+2. Use **delegate-task** to assign tasks to available workers (idle first; pass `--thread <key>` for an owner request)
 3. **Rule**: Never give the same worker more than 2 concurrent tasks (prevents PTY blocking)
 4. Include clear acceptance criteria in every delegation
 

package/config/skills/agent/core/ask-owner/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: Ask Owner
-description: Ask the owner ONE decision with 2–3 options, a default and a deadline. Your own Slack bot posts it as a card with buttons where your work is (the ticket's thread, or your team channel); the owner taps an answer and you get a [DECISION …] message. Never ask the owner open-ended questions in chat.
+description: Ask the owner ONE decision with 2–5 options, a default and a deadline. Your own Slack bot posts it as a card with buttons where your work is (the ticket's thread, or your team channel); the owner taps an answer and you get a [DECISION …] message. Never ask the owner open-ended questions in chat.
 version: 1.0.0
 category: communication
 skillType: claude-skill
@@ -52,12 +52,19 @@ bash execute.sh --question "Send the partner email on Monday?" \
 | Flag | Rule |
 |---|---|
 | `--question` | One line (8–280 characters). Name the decision, not "thoughts?" |
-| `--option` | 2–3 times. `"Label"` or `"Label — detail"`. The label is the button (≤ 40 characters). |
+| `--option` | 2–5 times, one per alternative. `"Label"` or `"Label — detail"`. The label is the button (short, ≤ 40 characters). The owner picks exactly one; the answer comes back as that label. |
 | `--default` | The option you will take if there is no answer by the deadline, or `wait` |
 | `--deadline` | Optional, ISO (`2026-10-02T12:00`). Default: tomorrow 12:00 |
 | `--ticket APP-12 --project P` | Optional. Ask about a ticket; the card goes in the ticket's thread, asked by its assignee |
 | `--sensitive email\|publish\|deploy\|spend` | Required for messages to outside people, public publishing, prod deploys, spending money. These are never auto-applied: the owner is re-asked once, then the question is parked |
 
+**"A or B?" is ONE card with options.** When the answers exclude each other (change it now / try the
+current version first), post a single ask with one `--option` per alternative. Never post two Yes/No
+cards for the two halves: the owner can tap Yes on both and you are left guessing. A second Yes/No
+ask on the same ticket within 60 seconds that reads as an either/or (starts with 还是 / 或者 / "or ",
+or the first one ends in an either/or) is rejected with an error telling you to post one card with
+options. Use plain Yes/No only for a single question with one possible action.
+
 What happens:
 
 - The card is posted by your own Slack bot:

package/config/skills/agent/core/ask-owner/execute.sh

@@ -1,5 +1,5 @@
 #!/bin/bash
-# ask-owner — one structured owner decision (question + 2–3 options + default
+# ask-owner — one structured owner decision (question + 2–5 options + default
 # + deadline), posted as a Slack card by the asking agent's own bot.
 # See specs/2026-10-01-decision-cards.md.
 set -euo pipefail

package/config/skills/agent/core/project-tickets/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: Project Tickets
-description: A project's own backlog — list, read, create, update, claim, release, assign, link, log and ask-owner (structured decision cards) on project tickets (markdown files in <project>/.crewly/tickets/, tracked in git), plus the per-project ticket autopilot switch, its stats and the daily retro.
+description: A project's own backlog — list, read, create, update, claim, release, assign, link, log and ask-owner (structured decision cards) on project tickets (markdown files in <project>/.crewly/tickets/, tracked in git), plus the per-project ticket autopilot switch, its speed mode, its stats, the daily retro and the self-review.
 version: 1.1.0
 category: task-management
 skillType: claude-skill
@@ -102,6 +102,11 @@ bash execute.sh create --project P --title "Export the report as CSV" \
   (orchestrator / team lead): create it with `--source request:<TKT id>` when
   it came in as a harness ticket, and tell the owner the new ticket id. Do not
   start working on it unless the owner asked for that too.
+- **Tickets you open for a goal replan** must name the goal metric they move
+  and the expected effect: `--metric "<goal metric> → <expected effect>"`
+  (e.g. `--metric "weekly /feed visitors → +150"`). It is written as the
+  description's first line (`Metric: …`). Without it the create is refused
+  with a message saying so — add the metric and create it again.
 
 ## Change a ticket
 
@@ -129,7 +134,7 @@ without a WorkItem). Team leads also have the `assign-ticket` skill.
 
 A **stopped** member is available: assigning starts it for the ticket (the
 answer's `wake` says `started`, or which gate refused it — then it picks the
-ticket up on its next start). Delegate by role; keep only lead-level work.
+ticket up on its next start). Role is a preference, not a limit: prefer an idle member; keep only lead-level work.
 
 ## Link work already in flight (orchestrator / team lead)
 
@@ -158,7 +163,7 @@ bash execute.sh ask-owner --project P --id APP-12 \
 bash execute.sh ask-owner --project P --id APP-12 --clear --note "resolved in the review call"
 ```
 
-ONE question with 2–3 options and a default (an option, or `wait`). The deadline defaults to
+ONE question with 2–5 options and a default (an option, or `wait`). The deadline defaults to
 tomorrow at 12:00. The ticket's assignee, else the lead, posts the question as a card in the
 ticket's Slack thread, using its own bot. The ticket gets `needs-owner` until the question is
 answered.
@@ -179,6 +184,7 @@ bash execute.sh autopilot --project P                       # show settings + st
 bash execute.sh autopilot --project P --on                  # switch on (the owner said so)
 bash execute.sh autopilot --project P --on --daily-budget 20M --max-in-flight 1   # budget in tokens
 bash execute.sh autopilot --project P --driver <lead session>   # or --driver default
+bash execute.sh autopilot --project P --speed rush          # rush | normal | chill | default
 bash execute.sh autopilot --project P --off
 ```
 
@@ -195,15 +201,41 @@ while an autopilot experiment on the project is running).
 
 When the project has a goal (its goals log or an active project OKR) but
 nothing is left to triage and someone on the team is idle, the team lead gets
-ONE `goal_replan` WorkItem: the goal, the tickets closed in the last 7 days,
-any open experiment card, and the ask "open the next tickets toward this goal,
-or say why there are none". The lead opens the tickets; the autopilot never
-makes them ready or starts work. At most `--replans-per-day <0-5>` a day
-(default 1; 0 = off), within the same daily budget and in-progress cap. A
-replan still open after `--replan-ttl-hours` (default 4) is expired. After a
-replan that opened no tickets the autopilot backs off (skips 2 days, then 4,
-then 7) until a new goal / OKR is set or a ticket is created. Only goals-log
-entries from the last 30 days count as an active goal.
+ONE `goal_replan` WorkItem: the goal, the lead's last self-review, the
+tickets closed in the last 7 days, any open experiment card, and the ask
+"open the next tickets toward this goal, or say why there are none". The lead
+opens the tickets (each with `--metric`); the autopilot never makes them ready
+or starts work. A replan still open after `--replan-ttl-hours` (default 4) is
+expired. Only goals-log entries from the last 30 days count as an active goal.
+
+**Speed** (`--speed`, the owner can also DM the orc "set CE to rush" /
+"CE 切到 chill"):
+
+| | Rush | Normal (default) | Chill |
+|---|---|---|---|
+| Replan when nothing is left | ≥ 1 h apart, ≤ 12 a day | ≥ 3 h apart, ≤ 4 a day | ≤ 1 a day |
+| Self-review | hourly | daily | weekly |
+| After a replan that opened nothing | retry in 1 h | next day | next week |
+| Daily budget when none is set | 50M | 20M | 8M |
+
+An explicit `--daily-budget` (and boosts) and `--replans-per-day <0-12>`
+(0 = off) override the speed's. A new goal / OKR or a new ticket lifts the
+wait after an empty replan.
+
+**Self-review**: at the speed's cadence the lead gets one short
+`autopilot_self_review` WorkItem (skipped when nothing changed and nobody is
+idle, never for a paused team or over the budget). File it, then complete the
+WorkItem:
+
+```bash
+bash execute.sh self-review --project P --gap "620 of 1,000 weekly visitors" \
+  --moved "CE-41 feed cards (+90)" --next-bet "two feed cards a day on the top search queries"
+```
+
+The status (`autopilot --project P`) and the evening digest show the latest
+self-review and why the autopilot stopped, if it did: `paused` (every team
+paused), `budget_reached`, `system_error` (failed work / a wake that never
+landed), `waiting_on_owner`, `no_ideas` (the last replan opened nothing).
 
 ## Autopilot numbers and retro (owner / orchestrator / team lead)
 

package/config/skills/agent/core/project-tickets/execute.sh

@@ -10,6 +10,7 @@
 #   bash execute.sh create  --project P --title "…" [--description "…"] [--acceptance "…" …]
 #                           [--priority P1] [--labels a,b] [--team <teamId>] [--status ready]
 #                           [--source request:TKT-012] [--request-id <id>] [--owner-review]
+#                           [--metric "<goal metric> → <expected effect>"]
 #   bash execute.sh update  --project P --id APP-12 [--title …] [--priority …] [--labels …]
 #                           [--description …] [--acceptance "…" …] [--status …] [--note "…"]
 #   bash execute.sh claim   --project P --id APP-12
@@ -23,11 +24,12 @@
 #   bash execute.sh ask-owner --project P --id APP-12 --clear [--note "answer"]
 #   bash execute.sh autopilot --project P [--on|--off] [--driver <session>|--driver default]
 #                             [--daily-budget <tokens, e.g. 20M>] [--max-in-flight <n>]      (owner / orchestrator)
-#                             [--retro on|off|default] [--replans-per-day <0-5>|default]
-#                             [--replan-ttl-hours <1-48>|default]
+#                             [--retro on|off|default] [--replans-per-day <0-12>|default]
+#                             [--replan-ttl-hours <1-48>|default] [--speed rush|normal|chill|default]
 #   bash execute.sh stats     --project P [--days 14] [--label feed]       (owner / orc / lead)
 #   bash execute.sh runs      --project P [--days 7] [--label feed]        (owner / orc / lead)
 #   bash execute.sh retro     --project P --day YYYY-MM-DD --summary "…" [--problem "class|title|detail|evidence" …]
+#   bash execute.sh self-review --project P --gap "…" [--moved "…"] --next-bet "…"
 #   bash execute.sh '{"action":"create","project":"P","title":"…"}'
 #
 # P = project id, name, or absolute path.
@@ -44,6 +46,10 @@ Usage:
   bash execute.sh create  --project P --title "…" [--description "…"] [--acceptance "…" …]
                           [--priority P0-P3] [--labels a,b] [--team <teamId>] [--status backlog|ready]
                           [--source request:TKT-012] [--request-id <id>] [--owner-review]
+                          [--metric "<goal metric> → <expected effect>"]
+                                                              --metric: the goal metric the ticket moves and the
+                                                              expected effect. Required for tickets you open during
+                                                              a goal replan (refused without it)
   bash execute.sh update  --project P --id APP-12 [--title …] [--priority …] [--labels …]
                           [--description …] [--acceptance "…" …] [--status …] [--note "…"]
   bash execute.sh claim   --project P --id APP-12             Take a ready ticket (creates your WorkItem)
@@ -56,7 +62,7 @@ Usage:
                                                               flight (a live WorkItem) to this ticket
   bash execute.sh ask-owner --project P --id APP-12 --question "…" --option "A" --option "B — detail"
                           --default "B"|wait [--deadline ISO] [--sensitive email|publish|deploy|spend]
-                                                              Ask the owner ONE question with 2–3 options. The
+                                                              Ask the owner ONE question with 2–5 options. The
                                                               ticket's assignee (else its lead) posts it as a card
                                                               in the ticket's Slack thread; the answer comes back
                                                               to that agent as a [DECISION …] message
@@ -64,15 +70,17 @@ Usage:
                                                               The owner answered: remove the needs-owner mark
   bash execute.sh autopilot --project P [--on|--off] [--driver <session>|default]
                           [--daily-budget <tokens, e.g. 20M>] [--max-in-flight <n>] [--retro on|off|default]
-                          [--replans-per-day <0-5>|default] [--replan-ttl-hours <1-48>|default]
+                          [--replans-per-day <0-12>|default] [--replan-ttl-hours <1-48>|default]
+                          [--speed rush|normal|chill|default]
                                                               Owner / orchestrator: show or change the ticket
                                                               autopilot (no flags = show). --retro: the lead's
                                                               daily retro (default: on while an autopilot
-                                                              experiment runs). --replans-per-day: how often a
-                                                              day the lead is woken to plan toward the goal when
-                                                              nothing is left to triage (default 1, 0 = off);
-                                                              --replan-ttl-hours: a replan still open after this
-                                                              long is expired (default 4)
+                                                              experiment runs). --speed: Rush (replan ≥1 h apart,
+                                                              ≤12/day, hourly self-review), Normal (≥3 h, ≤4/day,
+                                                              daily; the default) or Chill (≤1/day, weekly).
+                                                              --replans-per-day: a hard daily cap that overrides
+                                                              the speed's (0 = off); --replan-ttl-hours: a replan
+                                                              still open after this long is expired (default 4)
   bash execute.sh stats     --project P [--days 14] [--label feed]
                                                               Autopilot numbers per day: tickets triaged /
                                                               started / done / verified / sent back / stalled,
@@ -85,6 +93,9 @@ Usage:
                                                               Team lead: file the daily autopilot retro.
                                                               class = agent_judgment | missing_skill |
                                                               harness_gap | owner_dependency
+  bash execute.sh self-review --project P --gap "…" [--moved "…"] --next-bet "…"
+                                                              Team lead: file the autopilot self-review (gap to
+                                                              the target, what moved it, the next bet)
 
 P = project id, name or absolute path. Workers' new tickets start in backlog;
 the owner, the orchestrator or a team lead makes them ready.
@@ -97,6 +108,7 @@ ACCEPTANCE_JSON="null"
 HAS_DESCRIPTION=0
 QUESTION=""; CLEAR=""; OPTIONS_JSON="[]"; DEFAULT_OPT=""; DEADLINE=""; SENSITIVE=""; AP_ENABLED=""; AP_DRIVER=""; AP_BUDGET=""; AP_MAX=""
 AP_RETRO=""; AP_REPLANS=""; AP_REPLAN_TTL=""; DAYS=""; LABEL=""; DAY=""; SUMMARY=""; PROBLEMS_JSON="[]"
+METRIC=""; AP_SPEED=""; GAP=""; MOVED=""; NEXT_BET=""
 
 if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   J="$1"; shift
@@ -137,6 +149,11 @@ if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   DAY=$(printf '%s' "$J" | jq -r '.day // empty')
   SUMMARY=$(printf '%s' "$J" | jq -r '.summary // empty')
   PROBLEMS_JSON=$(printf '%s' "$J" | jq -c 'if (.problems|type) == "array" then .problems else [] end')
+  METRIC=$(printf '%s' "$J" | jq -r '.metric // empty')
+  AP_SPEED=$(printf '%s' "$J" | jq -r '.speedMode // .speed // empty')
+  GAP=$(printf '%s' "$J" | jq -r '.gap // empty')
+  MOVED=$(printf '%s' "$J" | jq -r '.moved // empty')
+  NEXT_BET=$(printf '%s' "$J" | jq -r '.nextBet // empty')
 fi
 if [[ -z "$ACTION" && $# -gt 0 && ${1:0:1} != '-' ]]; then ACTION="$1"; shift; fi
 
@@ -184,13 +201,19 @@ while [[ $# -gt 0 ]]; do
     --summary)       [ $# -ge 2 ] || error_exit "--summary requires a value";     SUMMARY="$2"; shift 2 ;;
     --problem)       [ $# -ge 2 ] || error_exit "--problem requires \"class|title|detail|evidence\""
                      PROBLEMS_JSON=$(jq -c --arg p "$2" '. + [($p | split("|")) as $f | {class: ($f[0] // "" | gsub("^\\s+|\\s+$"; "")), title: ($f[1] // "")} + (if ($f[2] // "") != "" then {detail: $f[2]} else {} end) + (if ($f[3:] | join("|")) != "" then {evidence: ($f[3:] | join("|"))} else {} end)]' <<<"$PROBLEMS_JSON"); shift 2 ;;
+    --metric)        [ $# -ge 2 ] || error_exit "--metric requires \"<goal metric> → <expected effect>\""; METRIC="$2"; shift 2 ;;
+    --speed|--speed-mode)
+                     [ $# -ge 2 ] || error_exit "--speed requires rush, normal, chill or default"; AP_SPEED="$2"; shift 2 ;;
+    --gap)           [ $# -ge 2 ] || error_exit "--gap requires a value";         GAP="$2"; shift 2 ;;
+    --moved)         [ $# -ge 2 ] || error_exit "--moved requires a value";       MOVED="$2"; shift 2 ;;
+    --next-bet)      [ $# -ge 2 ] || error_exit "--next-bet requires a value";    NEXT_BET="$2"; shift 2 ;;
     --full)          shift ;;
     --help|-h)       print_usage; exit 0 ;;
     *) error_exit "Unknown option: $1" ;;
   esac
 done
 
-[ -n "$ACTION" ] || { print_usage >&2; error_exit "Missing action: list | show | create | update | claim | release | assign | log | link | ask-owner | autopilot | stats | runs | retro"; }
+[ -n "$ACTION" ] || { print_usage >&2; error_exit "Missing action: list | show | create | update | claim | release | assign | log | link | ask-owner | autopilot | stats | runs | retro | self-review"; }
 
 # URL-encode a path segment (project paths contain slashes).
 enc() { jq -rn --arg v "$1" '$v|@uri'; }
@@ -217,7 +240,9 @@ case "$ACTION" in
     BODY=$(jq -n --arg title "$TITLE" --arg description "$DESCRIPTION" --argjson hasDescription "$HAS_DESCRIPTION" \
       --arg priority "$PRIORITY" --arg labels "$LABELS" --arg team "$TEAM" --arg status "$STATUS" \
       --arg source "$SOURCE" --arg requestId "$REQUEST_ID" --arg ownerReview "$OWNER_REVIEW" --argjson acceptance "$ACCEPTANCE_JSON" \
+      --arg metric "$METRIC" \
       '{title: $title}
+       + (if $metric != "" then {metric: $metric} else {} end)
        + (if $hasDescription == 1 then {description: $description} else {} end)
        + (if $acceptance != null then {acceptance: $acceptance} else {} end)
        + (if $priority != "" then {priority: $priority} else {} end)
@@ -294,11 +319,12 @@ case "$ACTION" in
     ;;
   autopilot)
     require_param "project" "$PROJECT"
-    if [ -z "$AP_ENABLED$AP_DRIVER$AP_BUDGET$AP_MAX$AP_RETRO$AP_REPLANS$AP_REPLAN_TTL" ]; then
+    if [ -z "$AP_ENABLED$AP_DRIVER$AP_BUDGET$AP_MAX$AP_RETRO$AP_REPLANS$AP_REPLAN_TTL$AP_SPEED" ]; then
       api_call GET "/project-ticket-autopilot/$(enc "$PROJECT")" | jq '{success, autopilot: .data}'
     else
-      BODY=$(jq -n --arg enabled "$AP_ENABLED" --arg driver "$AP_DRIVER" --arg budget "$AP_BUDGET" --arg max "$AP_MAX" --arg retro "$AP_RETRO" --arg replans "$AP_REPLANS" --arg ttl "$AP_REPLAN_TTL" \
+      BODY=$(jq -n --arg enabled "$AP_ENABLED" --arg driver "$AP_DRIVER" --arg budget "$AP_BUDGET" --arg max "$AP_MAX" --arg retro "$AP_RETRO" --arg replans "$AP_REPLANS" --arg ttl "$AP_REPLAN_TTL" --arg speed "$AP_SPEED" \
         '{}
+         + (if $speed == "default" then {speedMode: null} elif $speed != "" then {speedMode: $speed} else {} end)
          + (if $enabled != "" then {enabled: ($enabled == "true")} else {} end)
          + (if $retro == "default" then {retro: null} elif $retro != "" then {retro: $retro} else {} end)
          + (if $replans == "default" then {replansPerDay: null} elif $replans != "" then {replansPerDay: ($replans | tonumber? // $replans)} else {} end)
@@ -329,7 +355,14 @@ case "$ACTION" in
     BODY=$(jq -n --arg d "$DAY" --arg s "$SUMMARY" --argjson p "$PROBLEMS_JSON" '{day: $d, summary: $s, problems: $p}')
     api_call POST "/project-ticket-autopilot/$(enc "$PROJECT")/retro" "$BODY" | jq '{success, retro: .data, error}'
     ;;
+  self-review)
+    require_param "project" "$PROJECT"
+    require_param "gap (--gap)" "$GAP"
+    require_param "next bet (--next-bet)" "$NEXT_BET"
+    BODY=$(jq -n --arg g "$GAP" --arg m "$MOVED" --arg n "$NEXT_BET" '{gap: $g, nextBet: $n} + (if $m != "" then {moved: $m} else {} end)')
+    api_call POST "/project-ticket-autopilot/$(enc "$PROJECT")/self-review" "$BODY" | jq '{success, selfReview: .data, error}'
+    ;;
   *)
-    error_exit "Unknown action: $ACTION (use list | show | create | update | claim | release | assign | log | link | ask-owner | autopilot | stats | runs | retro)"
+    error_exit "Unknown action: $ACTION (use list | show | create | update | claim | release | assign | log | link | ask-owner | autopilot | stats | runs | retro | self-review)"
     ;;
 esac

package/config/skills/agent/core/project-tickets/execute.test.sh

@@ -88,6 +88,12 @@ run create --project p1 --title "Export CSV" --description "why" --acceptance "h
 check "create: path" "$(last .path)" "/api/project-tickets/p1"
 check "create: body" "$(last '.body | tostring')" '{"title":"Export CSV","description":"why","acceptance":["header row","opens in Excel"],"priority":"P1","labels":["ui","export"],"source":"request:TKT-012"}'
 
+# --- create with the goal metric (required for goal-replan tickets) ---
+run create --project p1 --title "Feed card 3" --metric "weekly /feed visitors → +150" --status ready >/dev/null
+check "create metric: body" "$(last '.body | tostring')" '{"title":"Feed card 3","metric":"weekly /feed visitors → +150","status":"ready"}'
+run '{"action":"create","project":"p1","title":"From JSON metric","metric":"returning visitors → +5%"}' >/dev/null
+check "create json metric: body" "$(last '.body | tostring')" '{"title":"From JSON metric","metric":"returning visitors → +5%"}'
+
 # --- create from JSON input ---
 run '{"action":"create","project":"p1","title":"From JSON","status":"ready","ownerReview":true}' >/dev/null
 check "create json: body" "$(last '.body | tostring')" '{"title":"From JSON","status":"ready","ownerReview":true}'
@@ -165,6 +171,19 @@ check "autopilot replans default: body" "$(last '.body | tostring')" '{"replansP
 run autopilot --project p1 --replan-ttl-hours 6 >/dev/null
 check "autopilot replan ttl: body" "$(last '.body | tostring')" '{"replanTtlHours":6}'
 
+run autopilot --project p1 --speed rush >/dev/null
+check "autopilot speed: body" "$(last '.body | tostring')" '{"speedMode":"rush"}'
+run autopilot --project p1 --speed default >/dev/null
+check "autopilot speed default: body" "$(last '.body | tostring')" '{"speedMode":null}'
+run '{"action":"autopilot","project":"p1","speedMode":"chill"}' >/dev/null
+check "autopilot speed json: body" "$(last '.body | tostring')" '{"speedMode":"chill"}'
+
+# --- self-review (specs/2026-10-04-autopilot-speed-modes.md) ---
+run self-review --project p1 --gap "620 of 1,000 weekly visitors" --moved "CE-41 feed cards" --next-bet "two cards a day on the top queries" >/dev/null
+check "self-review: path" "$(last .path)" "/api/project-ticket-autopilot/p1/self-review"
+check "self-review: body" "$(last '.body | tostring')" '{"gap":"620 of 1,000 weekly visitors","nextBet":"two cards a day on the top queries","moved":"CE-41 feed cards"}'
+check "self-review: missing next bet" "$(run_err self-review --project p1 --gap x | grep -c 'next bet')" "1"
+
 # --- stats / runs / retro (specs/2026-10-03-autopilot-experiments.md) ---
 OUT=$(run stats --project p1 --days 7 --label feed)
 check "stats: path" "$(last .path)" "/api/project-ticket-autopilot/p1/stats?days=7&label=feed"

package/config/skills/team-leader/delegate-task/SKILL.md

@@ -49,6 +49,46 @@ Assigns a task to a worker within the Team Leader's subordinate scope. Validates
 | `--from` | `fromSession` | No | Delegating TL's session name (for monitoring) |
 | `--request-id` / `-R` | `requestId` | No | Ticket this work is for: the id (or `TKT-123`) from the `[TICKET:TKT-123 <id>]` line of the message you are acting on. Omit it and the task is still linked when your current turn has exactly one ticket |
 | `--ticket` | `ticket` | No | Project ticket this work is for (e.g. `APP-12`). Without it a ticket is created for you when the target works on a project — see Project tickets |
+| `--thread` | `thread` | No | Owner request from Slack: the key from the `[SLACK-THREAD:<key>]` of the owner's message. The member answers the owner in that thread itself — see Owner requests |
+| `--no-member-fits` | `noMemberFits` | No | You keep the work: record what is missing (access, tool, permission, everyone busy). Needs `--task`; nothing is delegated — see No member fits |
+| `--work-item` | `workItemId` | No | With `--no-member-fits`: the WorkItem you keep (gets a `[NO-MEMBER-FITS]` note) |
+
+## Who to delegate to
+
+Role is a preference, not a limit: every member runs the same runtime and can
+code, write and research. Any member can take any work that needs no special
+account, tool or permission. Prefer an idle (or stopped) member over doing it
+yourself. Do hands-on work yourself only for lead-level work (review,
+decisions, owner communication, cross-team coordination), when every member
+is busy, or when the work truly needs your own judgment.
+
+## Owner requests (`--thread`)
+
+When the owner asked in Slack, pass the thread key from the owner message's
+`[SLACK-THREAD:<key>]`:
+
+```bash
+bash execute.sh --to sage-session --task "Goal: … Outcome: … Eval: …" --thread C0THINK:1790000000.000100
+```
+
+The WorkItem carries the thread and the member is told to post its progress
+and result there itself (`reply --work-item <id>`), under its own name. You do
+not relay its answer; the room's reply gate never holds the member's post.
+Without `--thread` the thread of your last owner message is used. (A thread
+in your DM with the owner: the member's bot cannot post there, so it answers
+in its own DM with the owner, opened with `Re: <task>`.)
+
+## No member fits (`--no-member-fits`)
+
+Rare. When you keep work yourself, record why — what is missing, not a role
+mismatch — so the owner sees missing roles in the daily report:
+
+```bash
+bash execute.sh --no-member-fits "needs the owner's Stripe login" --task "Update billing settings" [--work-item <id>] [--ticket CE-7]
+```
+
+Nothing is delivered. With `--work-item` the WorkItem gets a
+`[NO-MEMBER-FITS] <reason>` note.
 
 ## Project tickets