crewly 1.20.179 → 1.20.181

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

@@ -111,14 +111,14 @@ 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>"`; Crewly batches these to the owner's phone, you do not message the owner about them;
+- **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;
 - **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.
 
-**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` for the final step. When the owner's answer reaches you, act on it and clear the mark (`ask-owner --clear`).
+**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`.
 
 ---
 

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

@@ -97,14 +97,14 @@ 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>"`; Crewly batches these to the owner's phone, you do not message the owner about them;
+- **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;
 - **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.
 
-**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` for the final step. When the owner's answer reaches you, act on it and clear the mark (`ask-owner --clear`).
+**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`.
 
 ---
 

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

@@ -0,0 +1,79 @@
+---
+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.
+version: 1.0.0
+category: communication
+skillType: claude-skill
+assignableRoles:
+  - developer
+  - qa
+  - tpm
+  - designer
+  - frontend-developer
+  - backend-developer
+  - fullstack-dev
+  - qa-engineer
+  - product-manager
+  - architect
+  - generalist
+  - sales
+  - support
+  - team-leader
+  - orchestrator
+triggers:
+  - ask owner
+  - owner decision
+  - need approval
+  - needs your OK
+tags:
+  - communication
+  - decision
+  - slack
+execution:
+  type: script
+  script:
+    file: execute.sh
+    interpreter: bash
+    timeoutMs: 20000
+---
+
+# Ask Owner
+
+Use this when you need the owner to decide something. The owner reads it on a phone, so ask one
+concrete question and offer the real choices.
+
+```bash
+bash execute.sh --question "Send the partner email on Monday?" \
+  --option "Send Monday — after the review call" \
+  --option "Hold — wait for legal" \
+  --default "Hold"
+```
+
+| 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). |
+| `--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 |
+
+What happens:
+
+- The card is posted by your own Slack bot:
+  - a ticket ask goes in the ticket's thread;
+  - any other ask goes where your current work is, else as a new thread in your team channel.
+- The owner can answer by tapping a button, reacting (✅ default, ❌ "no", ⏰ tomorrow), replying in
+  the thread, or using the dashboard.
+- You receive `[DECISION D-7] The owner chose "…"`. Act on it. Do not ask again.
+- If nobody answers by the deadline, the default is applied and you are told. A `wait` default or a
+  sensitive ask never goes ahead without an answer.
+- Do not also message the owner about it. The card is the question.
+
+Withdraw a question you no longer need:
+
+```bash
+bash execute.sh --cancel D-7
+```
+
+A rejected ask (vague, missing options, etc.) comes back with an error that says what to fix.

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

@@ -0,0 +1,66 @@
+#!/bin/bash
+# ask-owner — one structured owner decision (question + 2–3 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
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+source "${SCRIPT_DIR}/../../_common/lib.sh"
+
+print_usage() {
+  cat <<'EOF_USAGE'
+Usage:
+  bash execute.sh --question "Send the partner email on Monday?" \
+    --option "Send Monday — after the review call" --option "Hold — wait for legal" \
+    --default "Hold" [--deadline 2026-10-02T12:00] [--ticket APP-12 --project P] \
+    [--sensitive email|publish|deploy|spend]
+  bash execute.sh --cancel D-7          Withdraw a question you no longer need
+  bash execute.sh '{"question":"…","options":["A","B"],"default":"A"}'
+EOF_USAGE
+}
+
+QUESTION=""; OPTIONS_JSON="[]"; DEFAULT_OPT=""; DEADLINE=""; SENSITIVE=""; TICKET=""; PROJECT=""; CANCEL=""
+
+if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
+  J="$1"; shift
+  QUESTION=$(printf '%s' "$J" | jq -r '.question // empty')
+  OPTIONS_JSON=$(printf '%s' "$J" | jq -c 'if (.options|type) == "array" then .options else [] end')
+  DEFAULT_OPT=$(printf '%s' "$J" | jq -r '.default // empty')
+  DEADLINE=$(printf '%s' "$J" | jq -r '.deadline // empty')
+  SENSITIVE=$(printf '%s' "$J" | jq -r '.sensitive // empty')
+  TICKET=$(printf '%s' "$J" | jq -r '.ticket // empty')
+  PROJECT=$(printf '%s' "$J" | jq -r '.project // empty')
+  CANCEL=$(printf '%s' "$J" | jq -r '.cancel // empty')
+fi
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --question|-q)  [ $# -ge 2 ] || error_exit "--question requires a value"; QUESTION="$2"; shift 2 ;;
+    --option|-o)    [ $# -ge 2 ] || error_exit "--option requires a value"
+                    OPTIONS_JSON=$(jq -c --arg o "$2" '. + [$o]' <<<"$OPTIONS_JSON"); shift 2 ;;
+    --default|-d)   [ $# -ge 2 ] || error_exit "--default requires a value"; DEFAULT_OPT="$2"; shift 2 ;;
+    --deadline)     [ $# -ge 2 ] || error_exit "--deadline requires a value"; DEADLINE="$2"; shift 2 ;;
+    --sensitive)    [ $# -ge 2 ] || error_exit "--sensitive requires a value"; SENSITIVE="$2"; shift 2 ;;
+    --ticket|--id)  [ $# -ge 2 ] || error_exit "--ticket requires a value"; TICKET="$2"; shift 2 ;;
+    --project|-p)   [ $# -ge 2 ] || error_exit "--project requires a value"; PROJECT="$2"; shift 2 ;;
+    --cancel)       [ $# -ge 2 ] || error_exit "--cancel requires a decision id"; CANCEL="$2"; shift 2 ;;
+    --help|-h)      print_usage; exit 0 ;;
+    *) error_exit "Unknown option: $1 (see --help)" ;;
+  esac
+done
+
+if [ -n "$CANCEL" ]; then
+  api_call POST "/decisions/$(printf '%s' "$CANCEL" | jq -sRr @uri)/cancel" '{}' | jq '{success, decision: (.data | {id, status})}'
+  exit 0
+fi
+
+require_param "question" "$QUESTION"
+BODY=$(jq -n --arg q "$QUESTION" --argjson o "$OPTIONS_JSON" --arg d "$DEFAULT_OPT" --arg dl "$DEADLINE" \
+  --arg s "$SENSITIVE" --arg t "$TICKET" --arg p "$PROJECT" \
+  '{question: $q, options: $o}
+   + (if $d != "" then {default: $d} else {} end)
+   + (if $dl != "" then {deadline: $dl} else {} end)
+   + (if $s != "" then {sensitive: $s} else {} end)
+   + (if $t != "" then {ticket: $t} else {} end)
+   + (if $p != "" then {project: $p} else {} end)')
+api_call POST "/decisions" "$BODY" \
+  | jq '{success, decision: (.data | {id, asker, status, deadline, posted: (.card != null), postError})}'

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

@@ -0,0 +1,62 @@
+#!/bin/bash
+# Tests for ask-owner — run with: bash execute.test.sh
+# A python HTTP stub plays the backend; asserts the calls and the output.
+set -u
+HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+EXEC="$HERE/execute.sh"
+PASS=0; FAIL=0
+check() {
+  local name="$1"; local got="$2"; local want="$3"
+  if [ "$got" = "$want" ]; then PASS=$((PASS+1)); else FAIL=$((FAIL+1)); echo "FAIL: $name"; echo "  want: $want"; echo "  got:  $got"; fi
+}
+
+PORT=18853
+STUB_LOG="$(mktemp)"; export STUB_LOG; export STUB_PORT="$PORT"
+python3 -u <<'PY' >/dev/null 2>&1 &
+from http.server import BaseHTTPRequestHandler, HTTPServer
+import json, os
+LOG = os.environ['STUB_LOG']; PORT = int(os.environ['STUB_PORT'])
+class H(BaseHTTPRequestHandler):
+    def reply(self, code, obj):
+        self.send_response(code); self.send_header('Content-Type', 'application/json'); self.end_headers()
+        self.wfile.write(json.dumps(obj).encode())
+    def do_GET(self):
+        return self.reply(200, {'success': True})
+    def do_POST(self):
+        n = int(self.headers.get('content-length', '0')); body = json.loads(self.rfile.read(n).decode() or '{}')
+        open(LOG, 'w').write(json.dumps({'method': self.command, 'path': self.path, 'body': body, 'agent': self.headers.get('X-Agent-Session')}))
+        if self.path.endswith('/cancel'):
+            return self.reply(200, {'success': True, 'data': {'id': 'D-7', 'status': 'cancelled'}})
+        if len(body.get('options', [])) < 2:
+            return self.reply(400, {'success': False, 'error': 'options are required: give the owner 2–3 concrete choices'})
+        return self.reply(201, {'success': True, 'data': {'id': 'D-7', 'asker': 'dev-ann', 'status': 'open', 'deadline': 'x', 'card': {'slackChannelId': 'C1'}}})
+    def log_message(self, *a, **k): pass
+HTTPServer(('127.0.0.1', PORT), H).serve_forever()
+PY
+STUB_PID=$!
+disown "$STUB_PID" 2>/dev/null || true
+trap 'kill "$STUB_PID" >/dev/null 2>&1; rm -f "$STUB_LOG"' EXIT
+for i in $(seq 1 30); do curl -s -o /dev/null -m 0.2 "http://127.0.0.1:${PORT}/" 2>/dev/null && break; sleep 0.1; done
+
+run() { CREWLY_SESSION_NAME=dev-ann CREWLY_API_URL="http://127.0.0.1:${PORT}" bash "$EXEC" "$@" 2>/dev/null; }
+run_err() { CREWLY_SESSION_NAME=dev-ann CREWLY_API_URL="http://127.0.0.1:${PORT}" bash "$EXEC" "$@" 2>&1 >/dev/null; }
+last() { jq -r "$1" "$STUB_LOG"; }
+
+OUT=$(run --question "Send the partner email on Monday?" --option "Send Monday — after review" --option "Hold" --default Hold --ticket APP-12 --project p1 --sensitive email)
+check "ask: path" "$(last .path)" "/api/decisions"
+check "ask: agent header" "$(last .agent)" "dev-ann"
+check "ask: body" "$(last '.body | tostring')" '{"question":"Send the partner email on Monday?","options":["Send Monday — after review","Hold"],"default":"Hold","sensitive":"email","ticket":"APP-12","project":"p1"}'
+check "ask: output" "$(printf '%s' "$OUT" | jq -c '.decision')" '{"id":"D-7","asker":"dev-ann","status":"open","deadline":"x","posted":true,"postError":null}'
+
+run '{"question":"Blue or green for the logo?","options":["Blue","Green"],"default":"wait"}' >/dev/null
+check "ask json: body" "$(last '.body | tostring')" '{"question":"Blue or green for the logo?","options":["Blue","Green"],"default":"wait"}'
+
+check "ask: server error reaches the agent" "$(run_err --question "Thoughts on this one?" --option "A" | grep -c 'options are required')" "1"
+check "ask: missing question" "$(run_err --option A --option B | grep -c 'question')" "1"
+
+OUT=$(run --cancel D-7)
+check "cancel: path" "$(last .path)" "/api/decisions/D-7/cancel"
+check "cancel: output" "$(printf '%s' "$OUT" | jq -c '.decision')" '{"id":"D-7","status":"cancelled"}'
+
+echo "ask-owner: $PASS passed, $FAIL failed"
+[ "$FAIL" -eq 0 ]

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 on project tickets (markdown files in <project>/.crewly/tickets/, tracked in git), plus the per-project ticket autopilot switch.
+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.
 version: 1.0.0
 category: task-management
 skillType: claude-skill
@@ -147,18 +147,30 @@ ticket already has another live WorkItem.
 New delegations need no `link`: `delegate-task` puts work for a teammate on a
 project through a ticket by itself (pass `--ticket APP-12` to use an existing one).
 
-## Ask the owner (orchestrator / team lead)
+## Ask the owner (assignee / team lead / orchestrator)
 
 ```bash
-bash execute.sh ask-owner --project P --id APP-12 --question "Send the draft to the 3 partners?"
-# the owner answered:
-bash execute.sh ask-owner --project P --id APP-12 --clear --note "owner: yes, Monday"
+bash execute.sh ask-owner --project P --id APP-12 \
+  --question "Send the draft to the 3 partners?" \
+  --option "Send Monday — after the review call" --option "Hold — wait for legal" \
+  --default "Hold" [--deadline 2026-10-02T12:00] [--sensitive email]
+# no longer needed (withdraws the open card and removes the mark):
+bash execute.sh ask-owner --project P --id APP-12 --clear --note "resolved in the review call"
 ```
 
-The ticket gets the `needs-owner` label and the question goes into its Log.
-With the ticket autopilot on, Crewly batches the open questions into one short
-message on the owner's phone — do not message the owner about them yourself.
-Keep the question to one line the owner can answer with a tap or a word.
+ONE question with 2–3 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.
+
+- **The answer** comes back to that agent as a `[DECISION D-7] The owner chose "…"` message,
+  and the ticket log records it.
+- **No answer by the deadline:** the default is applied.
+- **Sensitive asks** (`email` = messages to outside people, `publish`, `deploy` = production,
+  `spend`) are never auto-applied. The owner is re-asked once, then the question is parked.
+- Vague asks ("thoughts?") and asks without options are rejected, with an error that says what
+  to fix.
+- Do not message the owner about it yourself.
 
 ## Ticket autopilot (owner / orchestrator)
 

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

@@ -17,7 +17,9 @@
 #   bash execute.sh assign  --project P --id APP-12 --to <session> [--no-start]   (owner / orc / lead)
 #   bash execute.sh log     --project P --id APP-12 --note "progress"
 #   bash execute.sh link    --project P --id APP-12 --work-item <WorkItem id>   (owner / orc / lead)
-#   bash execute.sh ask-owner --project P --id APP-12 --question "…"            (owner / orc / lead)
+#   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]
+#                                                                               (owner / orc / lead / assignee)
 #   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 <usd>] [--max-in-flight <n>]      (owner / orchestrator)
@@ -47,10 +49,12 @@ Usage:
   bash execute.sh link    --project P --id APP-12 --work-item <id>
                                                               Orchestrator / team lead: tie work already in
                                                               flight (a live WorkItem) to this ticket
-  bash execute.sh ask-owner --project P --id APP-12 --question "…"
-                                                              Orchestrator / team lead: the ticket waits on the
-                                                              owner (label needs-owner); Crewly batches the
-                                                              question to the owner's phone
+  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
+                                                              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
   bash execute.sh ask-owner --project P --id APP-12 --clear [--note "answer"]
                                                               The owner answered: remove the needs-owner mark
   bash execute.sh autopilot --project P [--on|--off] [--driver <session>|default]
@@ -67,7 +71,7 @@ ACTION=""; PROJECT=""; ID=""; TITLE=""; DESCRIPTION=""; PRIORITY=""; LABELS="";
 STATUS=""; SOURCE=""; REQUEST_ID=""; NOTE=""; OWNER_REVIEW=""; ASSIGNEE=""; START="true"; WORK_ITEM=""
 ACCEPTANCE_JSON="null"
 HAS_DESCRIPTION=0
-QUESTION=""; CLEAR=""; AP_ENABLED=""; AP_DRIVER=""; AP_BUDGET=""; AP_MAX=""
+QUESTION=""; CLEAR=""; OPTIONS_JSON="[]"; DEFAULT_OPT=""; DEADLINE=""; SENSITIVE=""; AP_ENABLED=""; AP_DRIVER=""; AP_BUDGET=""; AP_MAX=""
 
 if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   J="$1"; shift
@@ -92,6 +96,10 @@ if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   WORK_ITEM=$(printf '%s' "$J" | jq -r '.workItemId // .workItem // empty')
   QUESTION=$(printf '%s' "$J" | jq -r '.question // empty')
   CLEAR=$(printf '%s' "$J" | jq -r 'if .clear == true then "true" else empty end')
+  OPTIONS_JSON=$(printf '%s' "$J" | jq -c 'if (.options|type) == "array" then .options else [] end')
+  DEFAULT_OPT=$(printf '%s' "$J" | jq -r '.default // empty')
+  DEADLINE=$(printf '%s' "$J" | jq -r '.deadline // empty')
+  SENSITIVE=$(printf '%s' "$J" | jq -r '.sensitive // empty')
   AP_ENABLED=$(printf '%s' "$J" | jq -r 'if (.enabled|type) == "boolean" then (.enabled|tostring) else empty end')
   AP_DRIVER=$(printf '%s' "$J" | jq -r '.driver // empty')
   AP_BUDGET=$(printf '%s' "$J" | jq -r '.dailyBudgetUsd // empty')
@@ -121,6 +129,11 @@ while [[ $# -gt 0 ]]; do
                      [ $# -ge 2 ] || error_exit "--work-item requires a value";   WORK_ITEM="$2"; shift 2 ;;
     --question|-q)   [ $# -ge 2 ] || error_exit "--question requires a value";   QUESTION="$2"; shift 2 ;;
     --clear)         CLEAR="true"; shift ;;
+    --option|-o)     [ $# -ge 2 ] || error_exit "--option requires a value"
+                     OPTIONS_JSON=$(jq -c --arg o "$2" '. + [$o]' <<<"$OPTIONS_JSON"); shift 2 ;;
+    --default)       [ $# -ge 2 ] || error_exit "--default requires a value";    DEFAULT_OPT="$2"; shift 2 ;;
+    --deadline)      [ $# -ge 2 ] || error_exit "--deadline requires a value";   DEADLINE="$2"; shift 2 ;;
+    --sensitive)     [ $# -ge 2 ] || error_exit "--sensitive requires a value";  SENSITIVE="$2"; shift 2 ;;
     --on)            AP_ENABLED="true"; shift ;;
     --off)           AP_ENABLED="false"; shift ;;
     --driver)        [ $# -ge 2 ] || error_exit "--driver requires a value";     AP_DRIVER="$2"; shift 2 ;;
@@ -222,12 +235,18 @@ case "$ACTION" in
     require_param "project" "$PROJECT"; require_param "id" "$ID"
     if [ "$CLEAR" = "true" ]; then
       BODY=$(jq -n --arg note "$NOTE" '{clear: true} + (if $note != "" then {note: $note} else {} end)')
+      api_call POST "/project-tickets/$(enc "$PROJECT")/$(enc "$ID")/ask-owner" "$BODY" \
+        | jq "{success, withdrawn: .data.withdrawn, ticket: (.data.ticket | ${TICKET_ROW})}"
     else
       require_param "question" "$QUESTION"
-      BODY=$(jq -n --arg q "$QUESTION" '{question: $q}')
+      BODY=$(jq -n --arg q "$QUESTION" --argjson o "$OPTIONS_JSON" --arg d "$DEFAULT_OPT" --arg dl "$DEADLINE" --arg s "$SENSITIVE" \
+        '{question: $q, options: $o}
+         + (if $d != "" then {default: $d} else {} end)
+         + (if $dl != "" then {deadline: $dl} else {} end)
+         + (if $s != "" then {sensitive: $s} else {} end)')
+      api_call POST "/project-tickets/$(enc "$PROJECT")/$(enc "$ID")/ask-owner" "$BODY" \
+        | jq "{success, decision: (.data.decision | {id, asker, status, deadline, posted: (.card != null), postError}), ticket: (.data.ticket | if . == null then null else ${TICKET_ROW} end)}"
     fi
-    api_call POST "/project-tickets/$(enc "$PROJECT")/$(enc "$ID")/ask-owner" "$BODY" \
-      | jq "{success, ticket: (.data | ${TICKET_ROW})}"
     ;;
   autopilot)
     require_param "project" "$PROJECT"

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

@@ -43,6 +43,10 @@ class H(BaseHTTPRequestHandler):
             return self.reply(200, {'success': True, 'data': {'workItem': {'id': body.get('workItemId')}, 'ticket': dict(T, status='in_progress', assignee='dev-bo', workItemId=body.get('workItemId'))}})
         if self.path.endswith('/claim'):
             return self.reply(200, {'success': True, 'data': {'claimed': True, 'workItem': {'id': 'wi-9'}, 'ticket': dict(T, status='in_progress', assignee='dev-ann', workItemId='wi-9')}})
+        if self.path.endswith('/ask-owner'):
+            if body.get('clear'):
+                return self.reply(200, {'success': True, 'data': {'ticket': T, 'withdrawn': 1}})
+            return self.reply(200, {'success': True, 'data': {'decision': {'id': 'D-1', 'asker': 'dev-ann', 'status': 'open', 'deadline': 'x', 'card': {'slackChannelId': 'C1'}}, 'ticket': dict(T, labels=['ui', 'needs-owner'])}})
         if 'forbidden' in self.path:
             return self.reply(403, {'success': False, 'error': 'Not allowed'})
         return self.reply(200, {'success': True, 'data': T})
@@ -119,12 +123,16 @@ run '{"action":"link","project":"p1","id":"APP-1","workItemId":"wi-43"}' >/dev/n
 check "link json" "$(last '.body | tostring')" '{"workItemId":"wi-43"}'
 check "link: missing work item" "$(run_err link --project p1 --id APP-1 | grep -c 'work-item')" "1"
 
-# --- ask-owner (orchestrator / lead): needs-owner mark with a one-line question ---
-run ask-owner --project p1 --id APP-1 --question "Send the draft to the partners?" >/dev/null
+# --- ask-owner: a structured decision (question + 2–3 options + default) ---
+OUT=$(run ask-owner --project p1 --id APP-1 --question "Send the draft to the partners?" --option "Send Monday — after review" --option "Hold" --default Hold --sensitive email)
 check "ask-owner: path" "$(last .path)" "/api/project-tickets/p1/APP-1/ask-owner"
-check "ask-owner: body" "$(last '.body | tostring')" '{"question":"Send the draft to the partners?"}'
-run ask-owner --project p1 --id APP-1 --clear --note "owner said yes" >/dev/null
+check "ask-owner: body" "$(last '.body | tostring')" '{"question":"Send the draft to the partners?","options":["Send Monday — after review","Hold"],"default":"Hold","sensitive":"email"}'
+check "ask-owner: output" "$(printf '%s' "$OUT" | jq -c '.decision')" '{"id":"D-1","asker":"dev-ann","status":"open","deadline":"x","posted":true,"postError":null}'
+run '{"action":"ask-owner","project":"p1","id":"APP-1","question":"Q is long enough?","options":["A","B"],"default":"wait","deadline":"2026-10-02T12:00"}' >/dev/null
+check "ask-owner json: body" "$(last '.body | tostring')" '{"question":"Q is long enough?","options":["A","B"],"default":"wait","deadline":"2026-10-02T12:00"}'
+OUT=$(run ask-owner --project p1 --id APP-1 --clear --note "owner said yes")
 check "ask-owner: clear" "$(last '.body | tostring')" '{"clear":true,"note":"owner said yes"}'
+check "ask-owner: clear output" "$(printf '%s' "$OUT" | jq -c '.withdrawn')" '1'
 check "ask-owner: missing question" "$(run_err ask-owner --project p1 --id APP-1 | grep -c 'question')" "1"
 
 # --- autopilot (owner / orchestrator): show or change the switch ---

package/config/skills/agent/core/reply/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: Reply
-description: Answer the message you are working on. It goes back where that message came from — Slack DM, Slack channel thread, or the Crewly chat/portal — without channel ids.
+description: Answer the work you are doing. It goes where that work came from — the owner's Slack DM or thread, the ticket's thread, or a new top-level post for scheduled work — without channel ids. --new-thread starts a new topic.
 version: 1.0.0
 category: communication
 skillType: claude-skill
@@ -43,10 +43,26 @@ Answer the message you are working on:
 bash config/skills/agent/core/reply/execute.sh "EFT 表改好了，附件是新版。"
 ```
 
-The harness remembers which message you are answering (the latest one
-delivered to you) and sends your answer back there, over the right path:
-the owner's Slack DM with you, the Slack channel thread, or the Crewly
-chat / portal conversation. You do not pass channel ids or thread keys.
+**Answer where you were asked; a new topic goes in a new thread.**
+
+The harness knows what you are working on and sends your answer where that
+work came from:
+
+| Your current work | Where the answer goes |
+|---|---|
+| a message from the owner | that conversation / Slack thread (DM, channel thread, Crewly chat / portal) |
+| a project ticket | the ticket's thread in your team channel (started on the first post) |
+| a scheduled / triggered task | the trigger's destination, else a NEW top-level post in your team channel |
+| nothing in particular | a new top-level post in your team channel |
+
+You do not pass channel ids or thread keys. A scheduled task's output never
+lands in an old, unrelated thread.
+
+To start a new topic yourself:
+
+```bash
+bash config/skills/agent/core/reply/execute.sh --new-thread "Wiki link audit" "Found 3 broken links: …"
+```
 
 Keep the `CREWLY_SESSION_NAME=<you>` prefix when your prompt shows one — it
 tells the system that you are the one replying.
@@ -58,6 +74,7 @@ tells the system that you are the one replying.
 | `"<text>"` / `--text` / stdin / `--text-file` | the reply |
 | `--interim` | a short note before the real answer (what you understood, how long); "working on it" stays up |
 | `--none` | nothing to answer (you answered elsewhere, or the message was not for you) |
+| `--new-thread "<title>"` | a new topic: a new top-level post in your team channel, opened with the title |
 | `--conversation <id>` / `--thread <key>` | only when your prompt tells you to answer somewhere specific |
 
 ## Rules

package/config/skills/agent/core/reply/execute.sh

@@ -1,8 +1,9 @@
 #!/bin/bash
-# reply — answer the message you are working on. The harness sends it back
-# where that message came from (Slack DM, Slack room thread, portal / Talk
-# chat) — no channel ids, no choosing between reply-channel / reply-chat /
-# reply-slack. Status lines ([DONE], [BLOCKED], …) still go to the
+# reply — answer the work you are doing. The harness sends it back where
+# that work came from (the owner's Slack DM / room thread / portal chat, the
+# ticket's thread, or a new top-level post for scheduled work) — no channel
+# ids, no choosing between reply-channel / reply-chat / reply-slack.
+# `--new-thread "<title>"` starts a new topic in your team channel. Status lines ([DONE], [BLOCKED], …) still go to the
 # orchestrator. See specs/2026-09-30-owner-message-guarantee.md §B.
 set -euo pipefail
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
@@ -16,12 +17,14 @@ Usage:
   bash execute.sh --text-file /path/reply.md
   bash execute.sh --interim "Got it — comparing the three quotes (~10 min)."
   bash execute.sh --none                       # no answer needed for this message
+  bash execute.sh --new-thread "Wiki link audit" "Found 3 broken links: …"   # a new topic
 
 Options:
   --text | -t        Reply text (or the first positional argument, or stdin)
   --text-file        Read the reply from a file
   --interim          A short note before the real answer; "working on it" stays up
   --none             Nothing to answer (already answered elsewhere / not for you)
+  --new-thread       Start a new thread in your team channel with this title (a new topic)
   --conversation|-C  Only if your prompt tells you to answer somewhere specific
   --thread | -T      Only if your prompt tells you to answer in a specific thread
   --help | -h        Show this help
@@ -33,6 +36,7 @@ INTERIM=""
 NONE=""
 CONVERSATION_ID=""
 THREAD=""
+NEW_THREAD=""
 
 while [[ $# -gt 0 ]]; do
   case "$1" in
@@ -43,6 +47,7 @@ while [[ $# -gt 0 ]]; do
     --none) NONE="1"; shift ;;
     --conversation|-C|--channel|-c) CONVERSATION_ID="$2"; shift 2 ;;
     --thread|-T) THREAD="$2"; shift 2 ;;
+    --new-thread) NEW_THREAD="$2"; shift 2 ;;
     --help|-h) print_usage; exit 0 ;;
     --) shift; if [[ $# -gt 0 && -z "$TEXT" ]]; then TEXT="$*"; fi; break ;;
     -*) echo "{\"success\":false,\"error\":\"Unknown option: $1\"}" >&2; print_usage >&2; exit 2 ;;
@@ -62,7 +67,7 @@ fi
 # Literal \n (from JSON-escaped text) → real newlines
 if [ -n "$TEXT" ]; then _NL=$'\n'; TEXT="${TEXT//\\n/$_NL}"; fi
 
-BODY=$(TEXT="$TEXT" INTERIM="$INTERIM" NONE="$NONE" CONVERSATION_ID="$CONVERSATION_ID" THREAD="$THREAD" python3 -c '
+BODY=$(TEXT="$TEXT" INTERIM="$INTERIM" NONE="$NONE" CONVERSATION_ID="$CONVERSATION_ID" THREAD="$THREAD" NEW_THREAD="$NEW_THREAD" python3 -c '
 import os, json
 p = {}
 if os.environ.get("NONE"):
@@ -75,6 +80,8 @@ if os.environ.get("CONVERSATION_ID"):
     p["conversationId"] = os.environ["CONVERSATION_ID"]
 if os.environ.get("THREAD"):
     p["thread"] = os.environ["THREAD"]
+if os.environ.get("NEW_THREAD"):
+    p["newThread"] = os.environ["NEW_THREAD"]
 print(json.dumps(p))
 ')
 

package/config/skills/agent/core/reply/execute.test.sh

@@ -78,6 +78,14 @@ LOG=$(cat "$STUB_LOG")
 check "conversationId" "$LOG" 'chan-9'
 check "thread" "$LOG" 'D0ABC:1790000000.000100'
 
+echo "test 4b: --new-thread"
+: > "$STUB_LOG"
+run_skill --new-thread "Wiki link audit" "Found 3 broken links" </dev/null >/dev/null 2>&1 || true
+LOG=$(cat "$STUB_LOG")
+check "newThread title" "$LOG" 'newThread'
+check "title text" "$LOG" 'Wiki link audit'
+check "body text" "$LOG" 'Found 3 broken links'
+
 echo "test 5: no text → error, nothing sent"
 : > "$STUB_LOG"
 if OUT=$(run_skill </dev/null 2>&1); then FAIL=$((FAIL + 1)); echo "  ✗ expected non-zero exit"; else PASS=$((PASS + 1)); echo "  ✓ non-zero exit"; fi

package/config/skills/agent/core/schedule-followup/SKILL.md

@@ -56,6 +56,10 @@ re-creating (#621).
   fires.
 - If you forget to cancel a done followup, it will still terminate itself.
   That's by design — we refuse to let followups live forever.
+- **Where the output goes:** a fired followup's answer is posted as a NEW
+  top-level message in the target's team channel (never an old thread).
+  Pass `--destination "#channel"`, `C…` or `C…:<ts>` to post it somewhere
+  specific.
 
 ## Examples
 
@@ -71,6 +75,10 @@ bash execute.sh --fire-at 2026-04-24T09:00:00Z \
 # Recurring with cap — will auto-stop after 3 tries even if you forget to cancel
 bash execute.sh --cron "0 * * * *" --max-fires 3 \
   --title "Poll Rex hourly (give up after 3)"
+
+# Quarterly review — post the result in a specific thread
+bash execute.sh --cron "0 9 1 */3 *" --title "Quarterly wiki review" \
+  --destination "C0123ABCD:1790000000.000100"
 ```
 
 ## Output

package/config/skills/agent/core/schedule-followup/execute.sh

@@ -43,6 +43,8 @@ Options:
   --name             Stable name (used for cancel / dedup). Auto-generated if absent.
   --max-fires        Stop after N fires (default: 1 for --in-minutes/--fire-at, unlimited for --cron)
   --max-idle-fires   Auto-cancel after N consecutive fires that produced no work (default: 3)
+  --destination      Where the output is posted: "#channel-name", a channel id (C…) or a thread (C…:<ts>).
+                     Default: a new top-level post in the target's team channel.
   --json      | -j   Raw JSON payload (same as legacy)
   --help      | -h   Show this help
 EOF_USAGE
@@ -59,6 +61,7 @@ DESCRIPTION=""
 NAME=""
 MAX_FIRES=""
 MAX_IDLE_FIRES="3"
+DESTINATION=""
 
 if [[ $# -gt 0 && ${1:0:1} == '{' ]]; then
   INPUT_JSON="$1"
@@ -77,6 +80,7 @@ while [[ $# -gt 0 ]]; do
     --name)               NAME="$2"; shift 2 ;;
     --max-fires)          MAX_FIRES="$2"; shift 2 ;;
     --max-idle-fires)     MAX_IDLE_FIRES="$2"; shift 2 ;;
+    --destination)        DESTINATION="$2"; shift 2 ;;
     --json|-j)            INPUT_JSON="$2"; shift 2 ;;
     --help|-h)            print_usage; exit 0 ;;
     --)                   shift; break ;;
@@ -103,6 +107,7 @@ if [ -n "$INPUT_JSON" ]; then
   NAME=$(printf '%s' "$INPUT_JSON" | jq -r '.name // empty')
   MAX_FIRES=$(printf '%s' "$INPUT_JSON" | jq -r '.maxFires // empty')
   MAX_IDLE_FIRES=$(printf '%s' "$INPUT_JSON" | jq -r '.maxIdleFires // "3"')
+  DESTINATION=$(printf '%s' "$INPUT_JSON" | jq -r '.destination // empty')
 fi
 
 # Validation
@@ -167,7 +172,9 @@ BODY=$(jq -n \
   --arg teamId "$TEAM_ID" \
   --arg maxFires "$MAX_FIRES" \
   --arg maxIdle "$MAX_IDLE_FIRES" \
+  --arg destination "$DESTINATION" \
   '{type:$type, config:$config, action:$action, createdBy:$createdBy, name:$name}
+   + (if $destination != "" then {destination:$destination} else {} end)
    + (if $teamId != "" then {teamId:$teamId} else {} end)
    + (if $maxFires != "" then {maxFires:($maxFires|tonumber)} else {} end)
    + (if $maxIdle != "" then {maxIdleFires:($maxIdle|tonumber)} else {} end)')