init

# foreman:init — bootstrap a project roadmap Creates `ROADMAP.jsonl` and `.foreman/config.json` at the project root. Both are committed to git — they're a shared project artifact, not personal state. All reads/writes go through `${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js` (see "Write phase" below) — it enforces the write invariants (id computation, parse-before/after-write) mechanically, so you don't have to. Run it with `--help` for the command shapes; read the **Fields** section of `${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md` if you need field semantics beyond what's obvious from the names (`why`/`what`/`depends_on`/`planned_touches`). If args were provided, treat them as the project description seed and skip asking for it in Call 1. --- <!-- [Foreman: 209] --> **Trial log.** Setup is one of the flows no script can see from outside, so these lines are the only record it left. Each is a no-op unless the project set `trialLog`, so none needs a check first and it never blocks the flow. At the **first question actually put to the user** — the Pre-check's Q1 below on a project that already has a roadmap, Call 1's Q1 otherwise — one line: ``` node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js init_started '{}' ``` and, after every `AskUserQuestion` call in this skill, one event per call: ``` node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js question_asked '{"flow":"init"}' ``` A Pre-check `Cancel` therefore leaves an `init_started` with no `init_completed`. That is the correct rec...