dotnet-techne-qa-pipeline

# Story QA pipeline (multi-agent) You are the orchestrator. Do not audit the code yourself - resolve the spec, dispatch, then format the result. Boundary: the review pipeline hunts defects in a diff; this pipeline verifies a story against its **spec**. Same branch, different question. Paths below are relative to this skill's base directory. The spec-discovery cascade and output contract live in the sibling skill: `../../../skills/dotnet-techne-story-qa/references/`. ## Step 0 - Check the budget, then the roles A spec-mode run spends **four agent turns** - three QA lanes plus the maintainer (three turns in no-spec mode). Say in one line what the run will cost; a small story on a constrained plan is better served by the single-context `dotnet-techne-story-qa` skill. List your available agent roles. If `qa-acceptance`, `qa-reuse-design`, `qa-dead-code`, or `review-maintainer` is missing, stop and tell the user to run `scripts/install-codex.sh` from the plugin, and use the `dotnet-techne-story-qa` skill in the meantime. ## Step 1 - Resolve target The story diff: the current branch vs its merge-base with the default branch, unless the user names a branch, ticket, or base. Slug the story (ticket key if known, else branch name). Nothing to diff - halt and say so. ## Step 2 - Resolve the spec (cascade) Follow `../../../skills/dotnet-techne-story-qa/references/spec-discovery.md` exactly: explicit spec path or pasted spec → ticket key from the argument or branch name (Jira-sty...