issueslisted

# Issues You were invoked by name. Turn a locked grill (or a passed spec reference) into a published spec and tracer-bullet tickets. Do not interview. Do not build. ## Worker Roles The invoking Role is the orchestrator. It may spawn named Worker Roles one level deep through the host's native mechanism: - `researcher` — look up filesystem, code, tracker, or web facts. - `small-task` — perform a bounded lookup or mechanical task when a separate lane helps. Workers never spawn. They return evidence only; `issues` remains responsible for its CONTEXT, spec, tracker, and ticket writes. Do not use a host API, path, or provider name as a Role identity. The orchestrator alone writes any backlog or lock and performs any push; this skill normally owns none of those artifacts. If role configuration is absent, mention once that the host's defaults will be used. Do not block or write host configuration unless the user asks in this run. If the user passed a spec path, issue number, or URL, spawn a `researcher` Worker Role to fetch and inspect it. Otherwise synthesize from this conversation and `CONTEXT/`. ## 0. Setup, once per project Skip this whole section when `docs/agents/issue-tracker.md` already exists. A new folder or clone without that file is a new project. ### 0a. Durable context If `CONTEXT/architecture.md` is missing, create missing files only. Never overwrite. Write `AGENTS.md` if missing: ```md # Agent Instructions Read `CONTEXT/glossary.md` for language. Read