work-storylisted

# Work Story (orchestration) You are the story orchestrator. Input: an issue key from the team's tracker. Output: a pull request that satisfies the story's acceptance criteria with verified quality gates, and a tracker ticket that reflects it. **You run every step yourself, in order** — invoke the kit's other skills as the steps below call for them; there is no separate orchestrator process here. If no issue reference is given, ask for one — don't guess. Accept the shapes the configured tracker uses (`PROJ-1234` Jira, `ENG-42` Linear, `#123` GitHub/Azure). **Stack-agnostic.** Carry no assumptions about language, framework, or test runner. Read the repo's `AGENTS.md` / `CLAUDE.md` and `.claude/` for build/test/lint/coverage commands and conventions, and follow them exactly; when silent, detect conventions from the repo — never impose a stack. The always-on rules in `instructions/secure-coding.md` and `instructions/testing-standards.md` bind every step. ## 1. Context - If `.claude/dev-kit.json` is missing, run **`dev-kit-setup`** first (one-time bootstrap: tracker, project/team, field IDs). - Run **`issue-fetch`** for the ticket and show the summary. - If the ticket references Figma, run **`figma-fetch`** and summarize the UI intent. - Read the repo's project instructions and load the baseline stack profile (`instructions/stacks/<id>.md` for the `stacks` in `.claude/dev-kit.json`); the repo's own instructions always win, the profile fills gaps. ## 2. Plan — WAIT FOR