write-goallisted

# Initiate a milestone and write Goal.md <HARD-GATE>Creation mode requires the current approved Decision and ROADMAP commits, a Milestone with `horizon: now` and `state: not-started`, and every declared prerequisite Milestone at `state: closed` with an `accepted_result`. Prepare the Goal and proposed initiation as one candidate; do not require a separate initiation authorization. Revision mode requires the current approved Goal plus its approved Decision and ROADMAP commits. If a prerequisite is missing or the changed meaning belongs to WhitePaper, Decision, or ROADMAP, stop and return the issue to `gmgn` for routing.</HARD-GATE> ## Language and writing rules Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing rules. Use the ROADMAP locale unless the owner changes it explicitly. Keep filename `Goal.md`, `type: goal`, and `nature: normative`. ## Working rhythm The primary orchestrator reads the approved WhitePaper, current Decision, and target ROADMAP Milestone, then forms the complete Goal meaning directly. Do not run a routine discovery or question checklist. It asks the Owner only when two or more interpretations remain consistent with upstream authority and the answer would change the active Milestone boundary or whether it can Close. Combine related blocking ambiguity into the smallest useful question, recommend one option, and state the real alternative and its effect on Requirement scope or Close. When resolved, di