Most ideas die in the gap
between the thought and
the first commit.

Ideas don’t arrive finished.

1. 01

   I have a rough thought.

   Does this belong in my project at all?

2. 02

   I have an opinion about it.

   Is it worth doing? What is the verdict, with reasons?

3. 03

   I have a scope.

   What exactly does this become — and what does it not?

4. 04

   I have a plan.

   What code changes, in what order, touching which files?

5. 05

   I have an implementation.

   The code exists. In an isolated worktree, with tests alongside.

6. 06

   I have acceptance tests.

   I will know it is done, because the finish line was written first.

7. 07

   I have a shipped thing.

   And I know exactly when — and why — it crossed the line.

Six columns.
Not a taxonomy. A spine.

A card moves right when the thinking on it has evolved enough to deserve the next column — not when a calendar or a standup says so. Each column is a different question the card has just finished answering.

1. 01

   Ideation

   The rough thought. No scope, no plan, no obligation.

2. 02

   Backlog

   Scoped and opinion-formed. A candidate the verdict let through.

3. 03

   Bugs

   A different shape of reasoning — from 'wrong' to 'fixed.'

4. 04

   In Progress

   Plan in place, worktree claimed, implementation underway.

5. 05

   Human Test

   Code written, acceptance list attached, waiting on a human.

6. 06

   Completed

   Shipped — and preserved, chain intact, for the next reader.

From thought, to argument, to artifact.

1. I

   It reads you, before you ask it to.

   On first run, Ideafy scans your repo and writes a Product Narrative — the problem, the people, the features, the stack. This becomes the lens every new idea is measured against. Not a rubric someone else wrote. Yours.

   — The narrative is a markdown file. You can edit it. It is yours.

2. II

   It argues with the idea, not you.

   Every card triggers an Ideafication pass: YAGNI, feasibility, complexity, an honest verdict. Weak ideas are told so, in writing, with reasoning attached. Strong ideas earn a plan. Sometimes the answer is don't build yet.

   — The verdict is never hidden. You can disagree — in writing.

3. III

   Only then, does it write code.

   When the argument holds, execution begins — in an isolated git worktree, with tests it drafted itself, on a branch that will not touch main until a human says so. The code is the footnote. The thinking is the text.

   — Autonomous or interactive. You choose, per card.

The Opinion tab,
writing itself.

One card, four tabs — Detail, Opinion, Solution, Tests. The screenshot below is the Opinion tab in the wild: the agent has read the Product Narrative, weighed YAGNI against feasibility, and filed a verdict in plain language. No mockups, no renderings, no stock UI.

The model proposes.
You still hold the pen.