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. Skim `${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md` if you need field semantics beyond what's obvious from the names (`why`/`what`/`depends_on`/`touches`). If args were provided, treat them as the project description seed and skip asking for it in Call 1. --- ## Pre-check If `ROADMAP.jsonl` already exists at the project root, ask before doing anything else: **Q1** — "ROADMAP.jsonl already exists. What do you want to do?" Options: `Overwrite it (start fresh — discards done entries and their accumulated notes)`, `Keep it, just add to it`, `Cancel` - Overwrite → continue to Call 1, the draft phase replaces the file. - Keep, add to it → skip straight to the draft phase, append new entries instead of replacing, don't touch `.foreman/config.json` if it already exists (ask the Call 2/Call 2b questions only if the config file is missing). - Cancel → stop here. --- ## Call 1 — project and goals (batch 2) **Q1** — "What is this project?" Options: `I'll describe it` (nudge the user to use Other and give a short description — what it does, what stack, new or existing codeba...