Ideas

A place for work that isn't specified yet. An idea is a lightweight pre-task prompt: a half-formed thought, a piece of friction, a "someone should…". Some earn a real task later; many do not, and that is the point.

Part of the brain.

Ideas exist so that noticing something does not force you to either specify it properly right now or lose it.

Where ideas come from#

  • You, via /toryo-idea from inside Claude, or board.
  • Any agent session, which can file one the moment it hits friction.
  • The end of a coding run. code-task's final step records process findings here rather than editing config inside a worktree that is about to be deleted, or polluting the task's pull request.
  • The session debugger, which files a rule-gap idea when it sees the same waste across several runs.

That last two are what make this a self-improvement loop rather than a notepad: friction observed while working becomes something you can triage later.

The model#

An idea has a kind (feature, process, or rule-gap) which keeps the triage list filterable, and a status: open, promoted, or dismissed. It is global or scoped to one project.

Recurrence is counted. Filing an idea identical to an existing open one bumps a counter instead of creating a duplicate. An idea reported eleven times is telling you something an idea reported once is not.

Triage#

Board's Ideas screen is where they get worked. Browse and filter, select several into one editable brief, and then act:

  • Dispatch it as a code-task run, straight from the composer
  • Copy it out into an interactive session
  • Mark it promoted or dismissed

Ideas scoped to a project dispatch against that project. All-global ideas dispatch as a project-less run rooted at a directory you choose.

Prefer filing an idea over creating a task when the work is not specified enough to plan yet. Promoting is cheap; unpicking a badly specified task is not.

Full command surface: CLI & contract reference.