Flow Creation: Automatic Triggers Design

Details

Raw Data

{
  "id": "ae2cf94f-badb-450f-8344-361bc97fa228",
  "type": "general",
  "status": "completed",
  "title": "Flow Creation: Automatic Triggers Design",
  "description": "Design options for when flows should automatically be created",
  "context": {
    "output": "<div style=\"background:#1e1e1e;color:#e0e0e0;padding:20px;border-radius:8px;font-family:'Consolas','Monaco',monospace;\">\n<h2 style=\"font-family:sans-serif;color:#fff;margin:0 0 16px 0;\">🌊 When Should a Flow Auto-Create?</h2>\n\n<p style=\"color:#98c379;margin-bottom:16px;\">You're right - if it requires conscious choice, it won't happen. Flows need to emerge naturally from work patterns.</p>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">The Core Insight</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\nA <span style=\"color:#e5c07b;\">flow</span> = a coherent piece of work with a goal\nA <span style=\"color:#e5c07b;\">session</span> = a conversation (may span multiple flows, or be part of one)\nA <span style=\"color:#e5c07b;\">turn</span> = a single prompt/response\n\n<span style=\"color:#7f848e;\">The question: What signals \"this is a new piece of work\"?</span>\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">Option A: Git Branch = Flow (Recommended)</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#98c379;\">Trigger:</span> First commit on a new branch creates a flow\n<span style=\"color:#98c379;\">End:</span> Branch merged/closed → flow completed\n\n<span style=\"color:#56b6c2;\">Pros:</span>\n  ✓ Natural git workflow - no new habits needed\n  ✓ Clear boundaries (branch = unit of work)\n  ✓ PRs map to flow completion\n  ✓ Already how most devs think about \"a piece of work\"\n\n<span style=\"color:#f44747;\">Cons:</span>\n  ✗ What about work on main? (hotfixes, docs)\n  ✗ Requires git - not all work is git-tracked\n  ✗ Some branches are long-running (develop)\n\n<span style=\"color:#c678dd;\">Fallback:</span> main branch work → \"maintenance\" flow per day\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">Option B: First Modifying Turn = Flow</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#98c379;\">Trigger:</span> First turn that uses Edit/Write/Bash creates a flow\n<span style=\"color:#98c379;\">End:</span> Session idle for 30min, or explicit \"done\"\n\n<span style=\"color:#56b6c2;\">Pros:</span>\n  ✓ Read-only exploration doesn't create flows\n  ✓ Work automatically grouped by session\n  ✓ Simple to implement\n\n<span style=\"color:#f44747;\">Cons:</span>\n  ✗ One long session = one giant flow\n  ✗ Multiple unrelated tasks get lumped together\n  ✗ Flow title unclear (from first prompt?)\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">Option C: Kontask Creates Flow</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#98c379;\">Trigger:</span> Each kontask IS a flow (or creates one)\n<span style=\"color:#98c379;\">End:</span> Kontask completed/approved\n\n<span style=\"color:#56b6c2;\">Pros:</span>\n  ✓ Already creating kontasks for significant work\n  ✓ Title/description already captured\n  ✓ Natural completion signal (approve/reject)\n\n<span style=\"color:#f44747;\">Cons:</span>\n  ✗ Multiple kontasks for one feature?\n  ✗ Not all work produces kontasks\n  ✗ Kontasks are outputs, flows are containers\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">Option D: Hybrid - Intent Detection (Smartest)</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#98c379;\">Triggers (any of):</span>\n  1. New branch detected → new flow\n  2. First prompt matches pattern → new flow\n     • \"Add...\", \"Fix...\", \"Implement...\", \"Update...\"\n     • \"Help me...\", \"I want to...\", \"Can you...\"\n  3. Significant time gap (>4h) + modifying turn → new flow\n  4. Explicit: \"Start flow: {title}\" in prompt\n\n<span style=\"color:#98c379;\">Continuation (same flow):</span>\n  • Same branch\n  • Follow-up prompts (\"now...\", \"also...\", \"next...\")\n  • Short time gap (<30min)\n  • References previous work\n\n<span style=\"color:#98c379;\">End:</span>\n  • PR merged / branch deleted\n  • Explicit: \"Done with this\" / \"Flow complete\"\n  • 24h idle with last action being commit\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">My Recommendation: Option D with Git Primary</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#c678dd;\">Default behavior:</span>\n\n1. <span style=\"color:#98c379;\">Branch-based</span> (primary signal)\n   git checkout -b fix-navbar-bug\n   → Auto-creates: Flow \"fix-navbar-bug\" (type: bugfix)\n   \n2. <span style=\"color:#98c379;\">Intent-based</span> (fallback for main branch)\n   \"Fix the navbar dropdown bug\"\n   → Auto-creates: Flow \"Fix navbar dropdown bug\" (type: bugfix)\n   \n3. <span style=\"color:#98c379;\">Time-based</span> (catch-all)\n   First turn after 4h gap on main\n   → Auto-creates: Flow \"Session 2026-01-09\" (type: other)\n\n<span style=\"color:#c678dd;\">Flow metadata auto-detected:</span>\n  • type: from keywords (\"fix\" → bugfix, \"add\" → feature)\n  • title: from branch name or first prompt\n  • priority: default medium, adjustable\n</pre>\n\n<h3 style=\"color:#61afef;margin:16px 0 8px 0;\">Implementation Simplicity</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#7f848e;\">Start simple, get smarter:</span>\n\n<span style=\"color:#98c379;\">Phase 1 (MVP):</span>\n  • Git branch = flow (simplest, highest value)\n  • main branch → daily \"maintenance\" flow\n  \n<span style=\"color:#98c379;\">Phase 2:</span>\n  • Intent detection from first prompt\n  • Better type/priority inference\n  \n<span style=\"color:#98c379;\">Phase 3:</span>\n  • Context-aware continuation\n  • Multi-flow sessions (\"also, unrelated...\")\n</pre>\n\n<div style=\"margin-top:16px;padding:12px;background:#2d2d2d;border-radius:6px;border-left:3px solid #98c379;\">\n<strong style=\"color:#98c379;\">💡 Bottom Line:</strong> Git branch is the strongest signal because it's <em>already</em> how you organize work. We detect the branch, auto-create a flow named after it, and everything in that session on that branch belongs to the flow. Zero new habits required.\n</div>\n</div>",
    "requestedAt": "2026-01-09T05:35:00.000Z",
    "requestId": "856d7e3b-f560-4f57-b46f-9560a01409eb",
    "choices": [
      {
        "label": "Git Branch = Flow",
        "value": "Implement Option A: Git branch creates flow automatically. Start with branch detection in konsole session creation.",
        "primary": true
      },
      {
        "label": "Hybrid Intent",
        "value": "Implement Option D hybrid: Git branch primary + intent detection fallback for main branch work"
      },
      {
        "label": "Keep Exploring",
        "value": "I have more questions about how flows should work before we decide on triggers"
      }
    ],
    "turnTiming": {
      "totalMs": 51905,
      "ttfeMs": 401,
      "thinkingMs": 51504,
      "toolExecutionMs": 0,
      "toolCallCount": 0,
      "thinkingPct": 99,
      "toolsPct": 0,
      "ttfePct": 1
    }
  },
  "createdBy": "claude",
  "createdAt": "2026-01-09T05:32:44.260Z",
  "updatedAt": "2026-01-09T05:32:48.777Z",
  "requestId": "856d7e3b-f560-4f57-b46f-9560a01409eb",
  "scope": "vibetools",
  "tags": [
    "gvFlow",
    "design",
    "automation"
  ],
  "targetUser": "claude"
}