Table of Contents generated with DocToc

• Issue management skill family
  • Family boundary
  • Skills
  • Adopter contract
  • Status
  • Cross-references

Issue management skill family

Scope. Works on any project, ASF or not — no Apache-Software-Foundation-specific assumptions baked in.

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

1. Agentic 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.
2. 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.
3. 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.
4. 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.
5. Stale-sweep — sweep open issues for inactivity past a configurable threshold, classify each as REQUEST-UPDATE (nudge) or CLOSE-STALE (pre-close notice), post one comment per issue on maintainer confirmation; closures require a second explicit confirmation step.
6. 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.
7. Deduplicate — identify two open issues sharing the same root cause, draft a cross-link comment and a closing rationale, and close the duplicate on maintainer confirmation; closures require a second explicit confirmation step.
8. Backlog stats — read-only dashboard over the open issue backlog. Surfaces a health rating, prioritised recommendations, age and staleness breakdowns, area pressure ranking, and a triage-funnel summary without modifying any tracker state.

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

issue-reproducer and issue-reassess-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:

Status

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

To provide pilot feedback, copy docs/pilot-report-template.md into your project notes, fill in each section, and optionally validate the filled-in report with:

uv run --project tools/pilot-report-validator pilot-report-validate <your-report.md>

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.