issue-orchestratelisted

Orchestrates a raw GitHub issue to an open, audit-trailed pull request per `spec/project/issue-orchestration/`. Comprehends the issue (body, comments, labels, linked items, repo surface), classifies it (`bug / feature-request / spec-change / security / docs / refactor / question / infra`), decomposes it into atomic specialist-ready work packages persisted as a pre-analysis artifact, routes large issues into the formal roadmap→feature→sprint pipeline, dispatches each package to the most specialised available skill or agent resolved by runtime lookup, and verifies via `quality-gate` and the standard PR flow. Invoke when the user asks to "analyse this issue", "orchestrate issue #N", "take this issue end-to-end", or equivalent German requests. Don't use to merge the PR (use `pull-request-merge`), to triage a red CI run (use `workflow-health-triage`), or to decompose an existing roadmap item (use `feature-decompose`). Supports resume per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · AI & Automation · score 76

Install: claude install-skill nolte/claude-shared

# Issue Orchestration Implements `spec/project/issue-orchestration/`. The skill is the generalist orchestrator that comprehends a raw GitHub issue, decomposes it into atomic specialist-ready work packages, dispatches the hands-on work to the most specialised available Claude skill or agent, and verifies the result through the standard pull-request gate. It never performs a work package's editing itself when a matching specialist exists; the quality-bearing core is the persistent pre-analysis artifact that prepares each sub-problem so a specialist can implement it completely. ## Why this is a skill, not an agent - **Externally-visible mutations gate on operator confirmation.** Issue-scope confirmation, the classification call, the pre-analysis approval, the route decision, each specialist dispatch, and the PR title / body are mid-flow operator dialogues; an agent's fire-and-forget shape would miss them. - **Orchestrator pattern (per `skill-vs-agent`).** The work is *analyse, decompose, route, dispatch, verify*; the dispatched specialist does the editing. The orchestrator stays in the main thread and chains other skills (`feature-decompose` or `roadmap-plan` for the pipeline route, `quality-gate`, `pull-request-create`). - **Multi-phase state accumulates across prompts.** A decomposition, a route decision, and a sequence of per-package dispatches span many turns; a skill's persistent instruction context and the resumable-work envelope fit this naturally. - Co