moradin-forgelisted

# moradin:forge The front door of the pipeline. You never guess what to do next in a forge project — this command reads the state and routes. ## When invoked `/moradin:forge` or `/moradin:forge <what the operator wants to do>` ## Step 1 — Find the target project The forge runs against a **target project directory** — always a SIBLING of the Moradin folder, never inside it (nesting tangles git and pollutes context). If the conversation already names it, use it. Otherwise ask: "Which project folder are we working in? (Give me a path, or a name and I'll create a new folder next to Moradin.)" For a brand-new project, create the sibling directory and `git init` it — explain in one sentence that git is the save-point system everything else relies on. ## Step 2 — Read the journal first Read `.forge/journal.md` in the target project. It is 3 lines: current stage, last action, next action. - **No `.forge/` directory** → first run. Go to Step 3 (Calibrate). - **Journal exists** → tell the operator where they are in one sentence ("You're mid-research; last time we compared databases. Next: run /moradin:decide.") Then route via Step 4. Load other `.forge/` files only when the route needs them — never all at once. ## Step 3 — Calibrate (first run only) Before asking anything: if this workshop has `memory/preferences/` content, read its `_INDEX.md` and pre-fill what's already known about how this operator works. Confirm pre-filled answers in one line ("I know you try the app rat