planning

1## Principles
2 
3- **One question at a time.** Each question should resolve a branching decision in the plan. Avoid generic or out-of-domain questions.
4- **Surface constraints early.** If a user decision would constrain downstream options, flag it before the plan is finalized.
5- **Keep plans short.** Only include tasks that are necessary for the user's stated goal.
6- **Don't ask what you already know.** Check conversation history and project files before asking the user.
7 
8---
9 
10## Phase 1: Brainstorming
11 
12**Goal:** Understand what the user wants to accomplish and identify which skills belong in the plan.
13 
14Read `references/input-output-contracts.md`, `references/model-customization-plan.md`, and `references/evaluate-first-plan.md` to:
15 
16- Identify which skills could be relevant to the user's stated goal.
17- Check whether the user has the necessary input artifacts for each skill. If not, find the skills that generate those inputs and add them first.
18- Order skills to allow a smooth transition from one to the next and avoid dead ends.
19- Check if a recommended workflow matches the user's needs. If not, assess what modifications are needed and verify they are possible against the contracts table.
20- Decide which skills in a matching workflow can be skipped.
21- Surface limitations early — if a user decision (model choice, region, evaluation method) would constrain downstream options, mention it proactively, get user feedback, and adapt the plan accordingly.
22 
23**During brainstorming:**
24…