Write Trace

Create a GitHub Trace issue — one pass over the Feature's Spine. The story and its scenarios already live in the Feature body. This skill selects a claim. It does not invent a spec.

Process

0. GitHub CLI setup

Run the setup check from ../references/gh-setup.md. Stop if gh is not installed or not authenticated. Note whether the extensions are available. That result controls whether native sub-issue and dependency links are created in step 10.

If invoked from wtf.feature-to-traces or wtf.write-feature, skip this step. The orchestrator already ran it. Also skip on re-invocations in the same session (e.g. "Next Trace in plan" loop in step 12).

Planning mode. If an orchestrator passed $WTF_PLAN, honor it per the Hand-offs rule in ../references/planning-mode.md: in flow, steps 2, 6, 9, and 12 do not ask — the passed plan entry is the claim, contracts derive from step 5 and the Feature's Domain Events, the orchestrator's consolidated review replaces step 9, and unanswerable facts return as NEEDS_INPUT. Standalone, the skill is always guided.

1. Identify the parent Feature and read its Trace state