create-issue

## Completion checklist (do this first) Before any of the pipeline's steps below, establish this seven-slot tracker. Establish it by working down these rungs, moving on whenever one is unavailable: `TodoWrite`, `TaskCreate`/`TaskUpdate`, `update_plan`, any candidate named in a runner-supplied listing of tools it has not yet exposed, then a runner-advertised discovery mechanism — used to search for those candidates, never as one itself. A candidate is **unavailable** when it is not exposed, when the call returns a failure, or when it returns without a failure but confirms no tracker, through the tool's own read-back where it exposes one or its rendered result otherwise. **No rung ends the run:** hold a breadcrumb naming any failure and carry on to the next rung. Once every candidate is exhausted, use the inline fallback in `references/fallback-no-task-tool.md`, loaded per the *Reference routing* rules below — the route this skill takes when the runner exposes no task-tracking tool or the exposed one is disabled or unusable. The seven slots: - [ ] 1. Run Step 1's arm and write its evidence artifact - [ ] 2. Clarify the user story until the Definition of Ready is met (Step 2) - [ ] 3. Draft the issue and pass the no-options gate (Step 3) - [ ] 4. Steelman the draft against the code, revise, re-pass the no-options gate, and append the steelman record to the derivation artifact (Step 3.5) - [ ] 5. Bootstrap the audit state, offer the fresh-context audit, and run and act on any...