spec-pulllisted

# Pull a Spec from the Tracker The start of dev work when a tracker item exists: the item is the source and the spec is its projection, so the verb is *pull*. One tracker item becomes `NNN-requirements.md`; **one item, one spec, for the life of the item** - re-run this skill whenever the item moves, and it updates the spec in place. A revision never spawns a second folder. Read-only by design: this skill never writes to the tracker - the board is the backlog, the repository is the record. A question the item cannot answer goes into the spec's `## Open questions`, and a question the item's author owns is relayed by the developer, never posted by the agent. ## Resolve the tracker (profile, then detect, then ask once, then STOP) 1. **Profile** `## Tracker`: `tracker`, `tracker_cli`, `tracker_item_ref` in `dev-project-profile.md`. 2. **Detect the forge's own tracker** from the git remote: GitHub remote -> `gh issue view <n> --json title,body,comments,url`; GitLab -> `glab issue view <n>`; Azure DevOps -> `az boards work-item show --id <n>`. The forge tracker needs no new dependency - the PR skills already require the same CLI. 3. **A connected MCP server** that can read the item is an accepted channel; name which server was used. 4. **Ask once** and record the answer in the profile. 5. **STOP** when nothing resolves or `tracker: none`: name exactly what is missing ("no tracker in the profile, remote is not a known forge, no tracker MCP server connected") and point to `spec-cr