From 16af308f1d32bfb39aebf1f955f74bb13b6625ef Mon Sep 17 00:00:00 2001 From: cryppadotta <34892728+cryppadotta@users.noreply.github.com> Date: Sun, 27 Sep 2026 02:11:33 +0000 Subject: [PATCH] docs: target cross-team scope questions to the requester Co-Authored-By: Paperclip --- skills/paperclip/SKILL.md | 2 +- skills/paperclip/references/api-reference.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/skills/paperclip/SKILL.md b/skills/paperclip/SKILL.md index a3f663bd3e1..88adfd8e33a 100644 --- a/skills/paperclip/SKILL.md +++ b/skills/paperclip/SKILL.md @@ -554,7 +554,7 @@ Exact response fields are documented in `skills/paperclip/references/api-referen - **Leave a next action.** Every progress comment should make clear what is complete, what remains, and who owns the next step. - **Prefer child issues over polling.** Create bounded child issues for long or parallel delegated work and rely on Paperclip wake events or comments for completion. - **Preserve workspace continuity for follow-ups.** Child issues inherit execution workspace from `parentId` server-side. For non-child follow-ups on the same checkout/worktree, send `inheritExecutionWorkspaceFromIssueId` explicitly. -- **Never cancel cross-team tasks.** If you question the task, record the concern and request a decision from the requester through a saved interaction. +- **Never cancel cross-team tasks.** If you question the task, follow the requester-directed decision flow in [Receiving cross-team work](references/api-reference.md#receiving-cross-team-work). Keep the task assigned to yourself; do not automatically hand it to a manager. - **Use first-class blockers** (`blockedByIssueIds`) rather than free-text "blocked by X" comments. - **Say only what you actually scheduled.** Never tell a user a "watcher"/monitor will wake you unless you scheduled a real issue monitor (non-null `monitorNextCheckAt`), and never imply a live watcher on a task you mark `done` — see **Monitors and Watchers**. - **On a blocked task with no new context, don't re-comment** — see the blocked-task dedup rule in Step 4. diff --git a/skills/paperclip/references/api-reference.md b/skills/paperclip/references/api-reference.md index 59b35f0989a..07d7a7253d7 100644 --- a/skills/paperclip/references/api-reference.md +++ b/skills/paperclip/references/api-reference.md @@ -684,7 +684,7 @@ When you receive a task from outside your reporting line: 1. **You can do it** — complete it directly. 2. **You can't do it** — record the missing capability or authority and follow [Handling blockers](#handling-blockers) below. -3. **You question whether it should be done** — you **cannot cancel it yourself**. Record the concern and request a decision from the requester through a saved interaction. +3. **You question whether it should be done** — you **cannot cancel it yourself**. Record the concern and request a decision through a saved interaction on the current task. If the requester is an agent, set `addresseeAgentId` to that agent and omit `resolverPolicy`; do not use the `human_only` example for an agent-directed question. If the requester is a user, set `addresseeUserId` to that user and `resolverPolicy: "human_only"`. Use `continuationPolicy: "wake_assignee"` and leave the task `in_review` while awaiting the answer. Keep the task assigned to yourself; this is a scope question, not a blocker handoff. **Do NOT** cancel a task assigned to you by someone outside your team.