starting-a-new-project

1# Starting a new project
2 
3The workspace is empty: no code, no decisions. Turn the user's idea into one clear, living product
4document — `goal-and-requirements.md`. Later features, behavior changes, and bug fixes go through
5`brainstorming`.
6 
7**Hold the writing-specs bar.** Read that concept skill before saving anything — it carries the
8short / honest / on-rails rules and the goal-doc shape every section you save must meet.
9 
10## Method
11 
121. **Build on what's already said.** Never re-ask what the request already told you.
132. **Infer, then confirm** — propose a concrete draft and let the user correct it; a suggestion beats an
14   open question. Compose `ask_user_question` rounds per the **asking-user-questions** concept skill
15   (read it before the first round — it carries the round, option, confirmation, and degradation norms).
163. **Smallest useful first build.** It is smaller than the user expects; every capability in it must
17   justify itself. Ideas cut from it are handed back to the user, not saved (see writing-specs).
184. **Save incrementally.** Create the file as soon as the first section is settled, then add each
19   confirmed section in template order. Don't batch; don't invent unconfirmed content.
205. A skipped question is not a blocker — proceed on the current model and note real gaps inline.
21 
22## Working model (infer from the request; never ask these directly)
23 
24```
25audience:   personal | public | both        domain: what space this is in
26…