spec-plan

# Spec Plan Write a proportional plan so clear that any engineer can follow it. The selected planning mode determines whether the plan stays in the conversation or becomes a persisted structured artifact. This skill does not write code. `atelier-orchestrator` owns automatic classification and the human may override it. When this skill is directly invoked without a selected mode, use Spec-backed Plan. If Inline planning reveals substantial design or coordination needs, ask the human whether to switch to a Spec-backed Plan before presenting the plan. ## Outputs ### Inline Plan (when explicitly selected) No repository artifact and no task tracker entry. Present the plan in conversation using: ```markdown ## context ## scope ## changes ## files ## validation ``` ## Inline Plan Workflow Read enough of the codebase to identify the current behavior, boundaries, affected files, and concrete validation. Keep the plan proportional. Populate every section: - `context`: Current behavior, relevant constraints, and why the change is needed - `scope`: Explicit in-scope and out-of-scope boundaries - `changes`: Ordered implementation changes at useful engineering granularity - `files`: Exact files expected to be created, modified, or deleted - `validation`: Concrete tests, checks, or manual verification Do not manufacture phases, task IDs, dependency graphs, acceptance matrices, `design.md`, `plan.json`, Beads issues, or harness todos. The conversation is the plan artifact. **T...