Launch deal: $99 lifetime for your first always-on AI system.
Build Lean SaaS cube logoBuild Lean SaaS
Back to Always-On Agents
Course lesson 9templateintermediate

Messy Input Routing

Turn raw ideas, voice notes, bookmarks, and chat messages into a calm routing system before anything becomes an execution ticket.

Austin Witherow
5 min read
Use the attached template

Most founders do not have an idea problem. They have a routing problem.

A good AI brain should let you capture messy inputs quickly without pretending every input deserves a ticket, task, PR, or sprint. The first job is not execution. The first job is routing.

Outcome for this lesson

By the end, you should have a simple intake note that can classify raw inputs into one of six destinations:

  1. archive only;
  2. use now;
  3. incubate;
  4. integrate into a workflow;
  5. research before action;
  6. discard.

Only the shaped, actionable work should become a GitHub Issue.

Why capture first, classify second

Raw inputs arrive in ugly forms:

  • a voice note while walking;
  • an X bookmark;
  • a customer quote;
  • a half-formed product idea;
  • a Discord message;
  • a screenshot;
  • a competitor page;
  • a bug report mixed with three unrelated thoughts.

If you force every input into your issue tracker, your tracker becomes a junk drawer. If you leave everything in chat, your assistant keeps asking you to repeat yourself.

The middle path is a capture note.

Step 1: create an inbox for raw captures

In your vault, create one boring place for raw captures:

Keep it simple. Do not build a database before you have a working habit.

Use this format:

Step 2: use the six routing tiers

1. Archive only

Use this when the input may be useful later but has no current job.

Examples:

  • interesting quote;
  • useful article;
  • possible future competitor angle;
  • reference image;
  • source you might cite later.

Next action: save it with context, then stop.

2. Use now

Use this when the input maps to an active task with a clear next step.

Examples:

  • bug on a live page;
  • customer asks for a specific change;
  • keyword opportunity for a page you are already editing;
  • missing acceptance criterion on an active issue.

Next action: update the active scratchpad or issue.

3. Incubate

Use this when the idea is promising but not ready.

Examples:

  • product idea without a clear buyer;
  • content angle without a target page;
  • feature idea that depends on another system;
  • vague “this could be big” thought.

Next action: move it to an incubator note with a review date.

4. Integrate into workflow

Use this when the input should change how the system works.

Examples:

  • repeated mistake;
  • recurring user preference;
  • better verification checklist;
  • new reusable command or script;
  • repeated routing rule.

Next action: update a workflow, skill, checklist, or operating note.

5. Research before action

Use this when acting now would mean guessing.

Examples:

  • “competitors are doing X” without examples;
  • SEO idea without query data;
  • product claim without evidence;
  • new tool recommendation without constraints.

Next action: create a small research question before creating implementation work.

6. Discard

Use this when the input is noise, stale, duplicated, off-strategy, or already handled.

Examples:

  • expired opportunity;
  • duplicate bookmark;
  • idea that conflicts with current strategy;
  • source with no credible value.

Next action: note why if useful, then delete or ignore.

Step 3: classify five real inputs

Pick five recent inputs from your actual workflow. For each one, fill this in:

The destination matters more than the wording. Every input should land somewhere sane or be intentionally dropped.

Step 4: protect your issue tracker

Use this rule:

A raw input is not an issue. A shaped action is an issue.

Before creating a GitHub Issue, the input should have:

  • a clear goal;
  • enough context for someone else to act;
  • a scope boundary;
  • acceptance criteria;
  • a verification expectation.

If it does not have those, it belongs in a scratchpad or research note first.

Copy this idea capture template

Verification checkpoint

You are done when:

  • five real inputs have routing decisions;
  • at least one input was intentionally not turned into a task;
  • every “use now” input links to a scratchpad, active issue, or clear destination;
  • your issue tracker contains shaped work, not raw idea fragments.

Next lesson

Once an input is shaped enough to execute, it needs a handoff object. Next, build the GitHub Issue format that lets an agent work without freelancing.

Next action

Keep this inside the course path

Continue the lesson sequence, install the skill when one exists, or use DevelopJoy when you want the workflow wired into your real workspace.