Ideas Workflow

Use the ideas workflow when you need a place to think, sketch, or explore before you are ready to commit to full project artifacts.

Ideas are intentionally lighter than projects: they are usually gitignored, personal, and optimized for brainstorming rather than traceable delivery.

Not Sure If It's an Idea Yet?

Direct entry to oat-idea-ideate requires an existing target — either a tracked idea record or an unchecked scratchpad seed in {IDEAS_ROOT}/scratchpad.md. For blank-slate brainstorms, route to oat-brainstorm instead.

If the thought is still pre-shape — you don't know whether it should land as a quick scratchpad note, a captured idea, a scoped backlog item, or a full project — start with oat-brainstorm. It's the project-independent brainstorming entry point: Hard Activation fires only on the brainstorm verb ("let's brainstorm", "brainstorm this", "can we brainstorm X", "help me brainstorm X", or /oat-brainstorm); ambiguous exploratory phrasing answers conversationally without the banner and offers structured mode only after sustained exploration. Once entered, it runs a structured design conversation and routes the outcome into the right destination (including this ideas workflow if that's where the brainstorm lands). Use ideas directly when you already know the work is "an idea worth tracking" and you want to capture or extend one without going through the dispatcher.

Contents

• Lifecycle - Capture, ideate, refine, and summarize an idea before promotion or discard.

When Ideas Fit Better Than Projects

• the problem is still fuzzy
• you want conversational exploration before writing a plan
• the work may never become a tracked deliverable
• you want local-only brainstorming that should not be committed yet

Key Differences from Projects

Promotion Path

When an idea becomes concrete, summarize it and then start a tracked OAT project in quick or spec-driven mode depending on design risk.