amend-roadmaplisted

# /amend-roadmap Mid-flight roadmap mutation. The user has a new task ("we need a caching layer task, depends on T05") and wants it in the roadmap WITHOUT hand-editing phases.yaml or the tracker. Skill ↔ verb split: this skill collects the fields, previews the plan, and confirms. ALL state mutation goes through `forge orchestrate amend-roadmap`, which is **tracker-first**: it creates the tracker issue, wires blocked-by relations, then materializes the task into `plans/phases.yaml` through the reconcile `--pull` machinery (staged addition) — phases.yaml stays single-writer. Every step is journaled and resumable. ## Preconditions - `plans/phases.yaml` exists, validates, and has a `source:` stanza (tracker-bound). If there is no `source:` stanza, stop: run `/push-to-tracker` (greenfield) or `/reconcile --pull` first. - `.forge/settings.yaml` has a working `tracker:` block. ## Step 1 — Collect fields Prompt the user for (one round, AskUserQuestion where it helps): | Field | Constraint | |---|---| | `phase` | existing `phase-N[.M]` id — show the active phases to pick from | | `title` | verb + noun, ≤ 8 words | | `description` | 1 paragraph | | `type` | foundation · data · backend · integration · content · infra · skill · docs | | `priority` | P0 · P1 · P2 | | `estimate` | S · M · L — **XL is refused by the verb** ("No XL tasks ship — split them") | | `owner_type` | backend-dev · frontend-dev · db-architect · devops-engineer · qa-engineer · security-auditor · design-engineer