threadlisted

# Thread reply Phase one of a two-phase workflow. This skill builds the picture. The `compose` skill writes the message. ## Hard rule: do not draft **Do not write a reply, a draft, or a suggested wording while this skill is running.** Not even a short one. Not even if the answer looks obvious. The real gate is the intent block in Step 5: never draft before it exists with a real `Position` and a real `Ask`, both something other than `not stated`. Until then, you gather and you wait, no matter how the user phrases it. If you think you have enough to draft, say so in one line and stop: "I think I have enough. Run /daikenja:compose when you are ready." ## Step 1: get the thread - **A link was given.** Use the available Slack or email tools to fetch the full thread, including the parent message and every reply. Do not work from the permalink text alone. - **Text was pasted.** Use it as-is. Do not go looking for more. - **Nothing was given.** Ask for a link or a paste. Do not search for it. If a fetch fails, say what failed and ask for a paste. Do not guess at the content. ## Step 2: summarize it Keep this to about 5 lines. The block below follows `${CLAUDE_PLUGIN_ROOT}/docs/response-format.md` -- read it before writing the reply; the summary is the answer and nothing precedes it. ``` Thread: [channel or subject, and how many messages] Asking: [who is asking, and what they actually want] Open: [what is still undecided] Waiting on you: [what, if anything, is yours] To