--- name: factory-plan description: Plan one issue the way the factory plans it, using Archon's sdlc planner. argument-hint: the issue to plan, as gh:issue: --- # factory-plan **The planner is Archon's, not ours.** ```bash archon workflow run archon-plan "Plan gh:issue:. Read MISSION.md and FACTORY_RULES.md first." ``` `archon-plan` ships bundled in the engine. It grounds itself against the current repository, writes `plan.md`, returns `ready`, and refuses to mutate the checkout while it does. **The automatic path does not call this.** `archon-ship` decides for itself whether an item needs planning, investigation or neither, and routes accordingly -- so running the planner on its own is what you do when you want that judgement separately, or when you want to read a plan before spending a delivery on it. ## If you want a different planner Put a workflow named `archon-plan` in your own `.archon/workflows/`. Project scope beats bundled, so yours wins with nothing here to change. That is the seam, not a fork. Note that acceptance deliberately does NOT trust a candidate-supplied workflow: the factory launches the trusted installed pack. An override changes what your factory builds with; it cannot change what judges the result. ## The one rule that outlives any planner Nobody reads the diff before it merges. A planner should declare `ready: false` rather than plan around an ambiguity it would normally raise in review, because there is no review to raise it in.