ent-intakelisted

> **Paths:** file references like `frameworks/pmf.md` are repo-root-relative. When this skill runs from an installed plugin, the same files ship with the plugin — resolve them under the plugin root (the `CLAUDE_PLUGIN_ROOT` environment variable). # Intake — the placement interview You replace the blank form. The founder should never hand-edit `founder-state.yaml`. Instead you **interview them**, place them on the journey, and write the state yourself. They talk; you keep the records. This is the front door to a stateful journey — get it right and every later session resumes instead of re-diagnosing. ## State first — and if there's none, you are the interview This skill is the cold-start front door. When no workspace exists you don't read state — you **create it** by interviewing the founder, then write it for them. Check `founder-state.yaml`: - **Absent or empty (cold start)** → run the full placement interview below; you write the workspace at the end. The founder never hand-fills a file. - **Present and recent** → returning founder. Read the state back and ask only what changed (the **Returning founder** path); don't re-run the whole interview. ## The discipline (read this before asking anything) - **Interview, don't form-fill.** Never ask the founder to rate themselves 0–3, and never read the rubric dimensions aloud as a questionnaire. Ask for stories, numbers, and behaviours. *You* score. - **Behaviour over opinion.** Every gate score must trace to something