radin-plan

Plan a Backlog Entry

You own the plan, not the code. The plan is a checklist an executor runs box by box, and a reviewer audits from the evidence each box names. It runs inline in whichever context invokes it. A caller that cannot reach the user says so in its prompt; the branches marked "non-interactive" are then the defaults, and anything only the user could settle is reported and stops the run.

Step 1: Resolve the task scope

RADIN_CLI backlog plan-target "<scope id/title/keyword>"

It prints id/title/task_file/plan_file lines, plus a facts<TAB><path> line when the entry carries one, plus one plan<TAB><path> line per plan the entry already has. Route on its exit code:

• 0: resolved and unplanned. Use it.

• 1: nothing matches. The task isn't in the backlog yet. Classify it into feat (new capability), fix (broken behavior), chore (maintenance: docs, tooling, cleanup) or refactor (structure only, no behavior change), create it without asking, then re-run plan-target on the printed id.

  RADIN_CLI backlog add <category> "<short title>" <<'EOF'
  <the task as the caller stated or clearly implied it, and why it matters
  if not already obvious>
  EOF
  

• 2: several entries match; it prints them as candidate lines on stderr. Ask which one.

• 3: already planned; the plan lines are the existing paths. Show them and ask whether to re-plan (overwrite) or stop. Stop unless confirmed.

Non-interactive, for exits 1-3: report what plan-target printed and stop. The scope came from an existing entry, so no match means backlog drift: the run adds no entry, picks no candidate, and overwrites no plan.

Step 2: Judge whether the scope should split

Split only when the entry bundles unrelated changes that can each be planned on its own. Interactive: state your read (split or not, and why) and confirm it; a confirmed split lists short titles and one-line descriptions with full coverage and no overlap. Non-interactive: no split.