/queue: an idea mid-build becomes a ticket, then a real plan, then a GitHub issue
Simulated example, not a record of real activity. The flow it illustrates: you are deep in building one thing and think of another. Instead of forgetting it, breaking flow to open a GitHub issue, or letting a notes file rot, one line goes into a per-project queue file. Later, "plan the next one" reads the actual codebase, writes a short spec, and promotes it to a GitHub issue that feeds the normal build flow.
SIMULATED EXAMPLE
You, mid-build
"oh, we should also do X" you do not want to stop
The queue
one file per project
one line, zero ceremony · nothing else changes
🧩 add a proof reminder
🩹 fix the date format
🧩 export to CSV
Plan it
"plan the next one"
reads the real code first, then writes a short spec you can say yes to