Implement Trace

Start an existing Trace as a developer.

Read the full spec (Trace + Feature + Epic). The Trace's contract is its Scenario Claim. Map the claim to the actual codebase. Propose a concrete technical approach. Drive implementation test-first against each claimed Gherkin scenario. Leave the system releasable on merge.

The expected Trace issue body structure is defined in @.github/ISSUE_TEMPLATE/TRACE.md.

Process

0. GitHub CLI setup

Run steps 1–2 of ../references/gh-setup.md (install check and auth check). If gh is not installed or not authenticated, stop. Extensions are not required for this skill.

If this skill was invoked from wtf.write-trace, wtf.loop, or another skill that already ran gh-setup this session, skip this step.

1. Identify the Trace

Call AskUserQuestion (per ../references/questioning-style.md):