setting-up-a-project

1# Setting up a project — dispatcher
2 
3The single entry point for turning a project into a spec graph. Figure out which situation you're in, then
4follow the matching skill — don't improvise the flow yourself.
5 
6## 1. Detect
7 
8Look at the workspace and use the spec tools (`spec_grep` / `spec_graph`):
9 
10- Is there already a spec graph (a `goal-and-requirements.md` or any `SPEC.md`)?
11- Is there real source code, or is the repo empty / near-empty (just a README or scaffolding)?
12 
13## 2. Route
14 
15| Situation | Follow |
16|---|---|
17| **Already has specs** | Don't redo it. Briefly offer to review/extend the graph (fill obvious gaps — a missing `architecture.md`, un-specced modules). Other work routes as usual: features, behavior changes, and bug fixes through `brainstorming`; work that changes no behavior proceeds directly. Declined → stop. Accepted → **Graph extension** below. |
18| **No specs · empty / near-empty repo** | The **`starting-a-new-project`** skill — interview the user to turn the idea into `goal-and-requirements.md`. |
19| **No specs · real source code** | The **`importing-a-codebase`** skill — analyze the code + agent files and draft the first spec graph, asking only for intent the code can't reveal. |
20 
21Read and follow that skill's steps.
22 
23## Graph extension (no dedicated skill)
24 
25No dedicated skill covers extending an existing graph. If the offer is accepted, align and adapt to
26the user's request with your own judgment, holding the **writing-specs** bar without a routing
27…