Loop 2 followup: start a side quest snippet, composes file-then-dispatch #3

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:27:16Z - https://github.com/coilysiren/voice-flow-learning-loop/issues/14

🤖 Filed by Claude Code on Kai's behalf.

Problem

Loop 2 layer 1 snippet-mining (#5) surfaced a recurring conversation shape Kai wants to compress into a single Snippet trigger. The pattern, almost verbatim across sessions:

Claude surfaces something worth doing mid-conversation.
Claude asks "should I coily ops gh issue create --repo coilysiren/... about this?"
Kai says "yes, and actually start working on it."

The two-step "file then dispatch" composition is the standing pattern. The dictation cost is the prose at step 3.

Proposed Snippet

Trigger: start a side quest
Expansion: file a ticket for this and start working on it

The trigger phrase is picked precisely because Kai would never say it in normal technical conversation. No collision risk.

The expansion is directive prose, not CLI. Wispr Flow emits literal text; Claude reads the prose and composes the two actions:

coily ops gh issue create --repo coilysiren/... against the thing just surfaced (Kai's existing accepted Snippet handles the literal CLI tokens).
coily dispatch interactive <new-issue-path> against the issue just created.

Meta-snippet because the trigger composes two lower-level Snippets via the agent, not by string concatenation.

Done when

The Snippet is entered into Wispr Flow.
Claude consistently routes the directive prose to the file-then-dispatch pipeline.
Kai has used it in real surfacing-mid-conversation moments and validated that "file the ticket and start working" lands without extra clarification.

Related: #5 (mining run), #13 (the bulk fan out variant - blocked on the repo-recall to Luca migration; this single-ticket variant is unblocked because it uses coily dispatch interactive directly).

_Originally filed by @coilysiren on 2026-05-20T12:27:16Z - [https://github.com/coilysiren/voice-flow-learning-loop/issues/14](https://github.com/coilysiren/voice-flow-learning-loop/issues/14)_ > 🤖 Filed by Claude Code on Kai's behalf. **Problem** Loop 2 layer 1 snippet-mining (#5) surfaced a recurring conversation shape Kai wants to compress into a single Snippet trigger. The pattern, almost verbatim across sessions: 1. Claude surfaces something worth doing mid-conversation. 2. Claude asks "should I `coily ops gh issue create --repo coilysiren/...` about this?" 3. Kai says "yes, and actually start working on it." The two-step "file then dispatch" composition is the standing pattern. The dictation cost is the prose at step 3. **Proposed Snippet** Trigger: `start a side quest` Expansion: `file a ticket for this and start working on it` The trigger phrase is picked precisely *because* Kai would never say it in normal technical conversation. No collision risk. The expansion is directive prose, not CLI. Wispr Flow emits literal text; Claude reads the prose and composes the two actions: 1. `coily ops gh issue create --repo coilysiren/...` against the thing just surfaced (Kai's existing accepted Snippet handles the literal CLI tokens). 2. `coily dispatch interactive <new-issue-path>` against the issue just created. Meta-snippet because the trigger composes two lower-level Snippets via the agent, not by string concatenation. **Done when** - The Snippet is entered into Wispr Flow. - Claude consistently routes the directive prose to the file-then-dispatch pipeline. - Kai has used it in real surfacing-mid-conversation moments and validated that "file the ticket and start working" lands without extra clarification. **Related:** #5 (mining run), #13 (the bulk `fan out` variant - blocked on the repo-recall to Luca migration; this single-ticket variant is unblocked because it uses `coily dispatch interactive` directly).

coilysiren

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