btw

/btw — Tangential Interjection Handler

When the user invokes /btw, they are injecting a thought that is tangential or unrelated to the current conversation thread.

Protocol

1. Acknowledge the interjection concisely (1-2 sentences max)
2. Classify it:
   • Actionable now: something to do immediately (e.g., "btw fix that typo on line 42")
   • Actionable later: save it and come back (e.g., "btw we should add tests for that module")
   • Note to self: record for future reference (e.g., "btw I've been thinking about X")
   • Feedback: guidance on behavior (e.g., "btw stop doing X")
3. Handle it:
   • If actionable now and trivial: do it inline, then resume the main thread
   • If actionable later: add to todo list or save to memory, then resume
   • If note/feedback: acknowledge and save to memory if worth persisting, then resume
4. Resume the main thread explicitly. State what you're returning to.

Key Rules

• Never let a /btw derail the main conversation. The whole point is controlled context injection.
• Keep your response to the /btw short. The user wants to get back to the main topic.
• If the /btw contains feedback about your behavior, treat it as high-priority — save it to memory.
• If the /btw contains a task, prefer adding it to the todo list over doing it immediately (unless trivial).
• Format: Start your acknowledgment with "Noted:" or "Got it:" to signal you've processed the interjection.

Examples

User: /btw you keep misspelling "foveated" as "foviated"
Agent: Noted — I'll watch for that. [saves feedback memory]
        Returning to the provider implementation...

User: /btw we should eventually add rate limiting to the MCP endpoint
Agent: Got it — added to the backlog. [adds todo or saves project memory]
        Back to the identity merge...

User: /btw can you fix the import on line 12 while you're in there
Agent: [fixes import]
        Done. Continuing with the refactor...