stdd-speclisted

# stdd-spec — Oath 遠征誓約 Opt-in skill (installed from `stdd-skills/`, not auto-loaded from the plugin's `skills/` directory). Precondition: if the change has a UI surface, `stdd-uiux`'s `design-ux.md` should exist before this skill finalizes the spec. Worked examples: `templates/spec.md`. Distilled reference: `references/gwt-and-rfc2119.md`. ## Step 0 — Entry triage (only when this change has no `STDD/<name>/` dir yet) If this change is entering the pipeline for the first time (no existing `STDD/<name>/` directory — not a follow-up action on an existing change), run the same four-point check `stdd-explore` runs before its own entry (don't duplicate the four points here — see `stdd-explore`'s Step 0 for the exact wording, or ask the user's earlier explore output if it already ran this check). If any point matches, refuse to start the STDD pipeline: reply that this change doesn't need the full STDD workflow and suggest handling it directly via ordinary conversation/existing workflow — never silently skip this check and generate `spec.md` anyway. If none match, continue to Step 1. ## Step 1 — Cross-check existing project spec/wiki content (before writing spec.md) If the target project already has prior STDD change directories (or a `wiki/`), before drafting this change's `spec.md`: - **External-ticket sourcing**: see `references/external-ticket-sourcing.md` for the full rule (when to dispatch `mirror-of-galadriel`, and how to degrade gracefully if it can't launch) — can