Capture, Clarify, Review

Raw ideas should not jump straight into execution. Good systems give ideas a shelf, a shape, and a review gate before they become public work.

Use a simple pipeline:

1. Capture: put the seed somewhere visible before it disappears.
2. Clarify: turn the seed into a task with outcome, context, boundaries, and a definition of done.
3. Ready: mark only work that someone can actually start without guessing.
4. Running: keep active work narrow enough to finish and review.
5. Review: check quality, safety, fit, and consequences before the work becomes public or irreversible.
6. Done or parked: finish deliberately, or defer deliberately.

Kanban shows state and ownership. The backlog is an idea refinery, not a junk drawer. Cron and other scheduled systems prepare recurring work, but they do not remove the need for judgment.

The useful boundary is not automation versus no automation. The useful boundary is whether each idea has the right state, enough context, clear permission, and a human review gate before it carries public weight.

---

See also: Automated First Pass, Human Final Review