Issue management skill family

Maintainer-facing skills for projects with a general-issue tracker (JIRA, GitHub Issues, Bugzilla, GitLab Issues). Five skills that cover per-issue work, pool-level sweeps, and read-only reporting:

Triage — sweep open issues in the configured candidate pool, classify against the project’s criteria, propose a disposition (BUG / FEATURE-REQUEST / NEEDS-INFO / DUPLICATE / INVALID / ALREADY-FIXED), execute on maintainer confirmation.
Reassess — sweep a configured pool of resolved or end-of-life issues and re-assess each against the current upstream codebase, surfacing silent fixes and partial fixes.
Reproducer — for a single issue identifying a code-level bug, extract the reporter’s example code, adapt it to run on the current default branch, execute via the project’s runtime, and compose a structured verdict. Read-only on the tracker.
Fix-workflow — for a triaged issue confirmed as a bug or feature, draft a fix PR (code change, regression test, commit message, PR description). Drafts only; the human committer reviews and pushes.
Stats — read-only dashboard over a directory of verdict.json files produced by reassess campaigns. Surfaces health rating, classification distribution, partial-fix surfaces, and per-component breakdowns.

Family boundary

This family sits alongside two related families:

pr-management-* handles the pull-request queue (open PRs, code review, queue stats). PRs are not issues; the skills there operate on a different tracker surface and apply different criteria.
security-issue-* handles the security- issue tracker, with confidentiality and CVE-allocation constraints the general-issue family does not need. A project may use both families against different trackers (private security repo; public general-issue JIRA).

A maintainer of a project with both an issue tracker and an active PR flow typically uses both issue-* and pr-management-* families, configured with different trackers.

Skills

Skill	Mode	Purpose
`issue-triage`	Triage	Per-issue classification + disposition proposal
`issue-reassess`	Triage	Pool-level sweep of resolved / EOL issues for re-assessment
`issue-reproducer`	—	Per-issue extraction + execution of code examples
`issue-fix-workflow`	Drafting	Drafts a fix PR for a triaged issue
`issue-reassess-stats`	—	Read-only campaign dashboard

Reproducer and stats sit outside the MISSION mode taxonomy; they are mechanical / read-only, not classificatory or mutating.

Adopter contract

The skills resolve project-specific content from these files in the adopter’s <project-config>/ directory:

File	Used by
`project.md`	all `issue-*` skills (identifiers, `upstream_default_branch`)
`issue-tracker-config.md`	all `issue-*` skills (URL, project key, auth, default queries)
`scope-labels.md`	`issue-triage`, `issue-reassess` (component / area routing)
`release-trains.md`	`issue-triage` (`@`-mention routing)
`canned-responses.md`	`issue-triage` (NEEDS-INFO templates)

Additional template files added by this family (forthcoming):

runtime-invocation.md — how to invoke the project’s runtime; consumed by issue-reproducer for executing extracted code.
reassess-pool-defaults.md — pool definitions extending the default queries in issue-tracker-config.md.
reproducer-conventions.md — evidence-package directory layout for issue-reproducer output.

Status

Experimental. No adopter pilot has run an evaluation against this family yet. Shape may change between framework versions.

Cross-references

Top-level README — Adopting the framework — 3-step bootstrap.
projects/_template/README.md — adopter scaffold index.
docs/modes.md — MISSION mode taxonomy that the mode: frontmatter field declares against.
docs/setup/agentic-overrides.md — the override mechanism every skill in this family supports.