Loop 2 followup: spin this up snippet, dispatch-only on an existing ticket #2

New issue

Closed

opened 2026-05-23 20:55:37 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-23 20:55:37 +00:00

Owner

Originally filed by @coilysiren on 2026-05-20T12:34:59Z - https://github.com/coilysiren/voice-flow-learning-loop/issues/15

🤖 Filed by Claude Code on Kai's behalf.

Problem

The side-quest Snippet (#14) handles file then dispatch in one go. Distinct case: a ticket already exists, and Kai wants to spawn a coily dispatch interactive session on it without re-filing. Common shapes:

Mid-conversation Kai is looking at an existing GH issue and wants to hand it off.
A previous session surfaced a backlog ticket worth picking up now.
Kai dictates the issue ref or URL and wants Claude to dispatch on it.

The dictation cost today is the prose "start a coily dispatch interactive session on this ticket" or similar. Compressible.

Proposed Snippet

Trigger: spin this up
Expansion: $$dispatch a session on this ticket$$

Trigger satisfies the orthogonality constraint (see #14 comment): "spin this up" is not how Kai would naturally refer to dispatch in technical conversation, so no false fires.

Expansion is wrapped in the $$...$$ Snippet marker (also #14 comment). Claude reads the directive, resolves "this ticket" from current chat context (the issue ref or URL most recently surfaced or pasted), and runs coily dispatch interactive <issue-path>.

Done when

The Snippet is entered into Wispr Flow.
The $$...$$ recognition rule is in agentic-os-kai/AGENTS.md (shared dependency with #14).
Claude consistently resolves "this ticket" from context and dispatches without re-asking.
Kai has used it in real chat-and-dispatch moments.

Trigger candidates considered:

spin this up (picked - two short syllables each side, no collision)
hand it off (close runner-up)
send it downrange
queue this up (rejected - "queue" collides with normal usage)

Related: #5 (mining run), #13 (the bulk fan out variant, blocked on the repo-recall to Luca migration), #14 (the file-then-dispatch sibling; carries the $$ marker + orthogonality conventions that apply here too).

_Originally filed by @coilysiren on 2026-05-20T12:34:59Z - [https://github.com/coilysiren/voice-flow-learning-loop/issues/15](https://github.com/coilysiren/voice-flow-learning-loop/issues/15)_ > 🤖 Filed by Claude Code on Kai's behalf. **Problem** The side-quest Snippet (#14) handles *file then dispatch* in one go. Distinct case: a ticket already exists, and Kai wants to spawn a `coily dispatch interactive` session on it without re-filing. Common shapes: - Mid-conversation Kai is looking at an existing GH issue and wants to hand it off. - A previous session surfaced a backlog ticket worth picking up now. - Kai dictates the issue ref or URL and wants Claude to dispatch on it. The dictation cost today is the prose "start a coily dispatch interactive session on this ticket" or similar. Compressible. **Proposed Snippet** Trigger: `spin this up` Expansion: `$$dispatch a session on this ticket$$` Trigger satisfies the orthogonality constraint (see #14 comment): "spin this up" is not how Kai would naturally refer to dispatch in technical conversation, so no false fires. Expansion is wrapped in the `$$...$$` Snippet marker (also #14 comment). Claude reads the directive, resolves "this ticket" from current chat context (the issue ref or URL most recently surfaced or pasted), and runs `coily dispatch interactive <issue-path>`. **Done when** - The Snippet is entered into Wispr Flow. - The `$$...$$` recognition rule is in `agentic-os-kai/AGENTS.md` (shared dependency with #14). - Claude consistently resolves "this ticket" from context and dispatches without re-asking. - Kai has used it in real chat-and-dispatch moments. **Trigger candidates considered:** - `spin this up` (picked - two short syllables each side, no collision) - `hand it off` (close runner-up) - `send it downrange` - `queue this up` (rejected - "queue" collides with normal usage) **Related:** #5 (mining run), #13 (the bulk `fan out` variant, blocked on the repo-recall to Luca migration), #14 (the file-then-dispatch sibling; carries the `$$` marker + orthogonality conventions that apply here too).

coilysiren

2026-05-30 05:43:41 +00:00