0006: `orion new` and the plan stage are sequential phases, not two front doors
- Status: Accepted
- Date: 2026-08-28
Contextβ
orion new "<idea>" starts an interactive conversation (discovery) before
anything is derived, because the intent, spec and plan stages run through
claude -p and cannot ask the user anything once started β one ambiguous
premise there propagates into spec, plan, scaffold and the tracker tree,
costing far more to unwind than the conversation would have cost to have.
There was a question of whether interactive discovery and the async plan
stage should instead be two independent entry points a user picks between.
Decisionβ
orion new and the plan stage are sequential phases of one flow, not two
front doors, with the Jira project (created at orion provision) as the
handoff artifact between them.
Consequencesβ
- Interactive interrogation belongs in
new, because a human is present at that point to answer it. - The
planstage (and the stages after it β scaffold, decompose) keeps the async discovery gate instead: unresolved Open questions in the intent file block those stages until answered in the file itself, because by the timeplanruns no human is assumed present to prompt. - A user cannot skip straight to
planexpecting an interactive prompt; ambiguity there surfaces as a blocking open question in the artifact, not a conversation.