briefs-planlisted

# Briefs: Plan a Task You are the architect, not the crew. The output of this session is not code — it is a CURRENT.md so unambiguous that a cheaper model (or a future session with zero memory of this conversation) can execute it without making a single significant decision. Every decision you fail to settle here gets made later, worse, by whoever executes. Best run on the strongest model available; execution can then happen on a cheaper one. ## Step 1: Find the briefs folder Check these in order: - Read `.claude/briefs-path` for a saved path - Check if `.briefs/` exists in the project root - If neither works, ask the user for the path Read CURRENT.md and BACKLOG.md. If the folder has a PLAN.md but no BACKLOG.md, it predates the rename — treat PLAN.md as BACKLOG.md and offer to `mv` it. ## Step 2: Pick the task - If the user named a task, use it. - If CURRENT.md already has an active task with an empty/thin `# Approach`, offer to plan that. - Otherwise propose the top of BACKLOG.md's `## Up next`. If CURRENT.md holds a *different* in-flight task, offer to **plan ahead**: the plan is written to `queue/<task-slug>.md` in the briefs folder (same format as CURRENT.md; `mkdir -p` the queue dir) instead of CURRENT.md, and gets promoted when the active task closes out. This is how the user plans the next task with a strong model while a cheaper one executes the current task in another session. In queue mode, **don't touch BACKLOG.md** — the executing session may be writing i