Triage, groom, prioritize, and file GitHub issues across the backlog lifecycle.
npx skills add https://github.com/chris-prener/dev-kit --skill backlog-chris-prener
Please help me install this Agent Skill. Skill: backlog Source: https://github.com/chris-prener/dev-kit/tree/main/dev-kit/skills/backlog Command: npx skills add https://github.com/chris-prener/dev-kit --skill backlog-chris-prener
needs-grooming label to a fully baked issue with user story, parent epic linkage, and Definition-of-Ready pre-flight checks. - Groom and Triage: Periodically curate the needs-grooming inbox, walk ROADMAP horizons, kill stale issues, regroup orphans, and route needs-triage issues to epics, standalone status, duplicate, or not-planned — every mutation confirmed per item. - Prioritize and Auto-file: Suggest implementation order across open issues, and let other skills (QC, doc-audit, code-review) file durable findings non-interactively with dedup markers. - Use Case: After a code review surfaces a tech-debt finding, auto-file it as a labeled GitHub issue with dedup protection, then later run groom-inbox to promote captured ideas into triaged, epic-linked work items. ## Quick Start Ask Claude to groom the backlog by walking the needs-grooming inbox and promoting ready issues to triage.High-intent search queries and answers about installing and using this skill.
Invoke the backlog skill's Groom operation, which walks issues labeled needs-grooming, fills in deferred sections like problem statement and acceptance criteria, runs a Definition-of-Ready pre-flight check, and promotes each issue to needs-triage with per-item confirmation.
The Triage operation lists open issues carrying the needs-triage label via gh issue list, runs a dedup search and epic-linkage check on each, then proposes one of six routes — epic link, standalone, duplicate, not-planned, promote-to-epic, or defer — confirming before any mutation.
needs-grooming marks half-formed captured ideas awaiting full authoring during grooming, while needs-triage marks fully baked issues awaiting routing to an epic, standalone status, or closure. Grooming promotes issues from the first label to the second.
No. Epic promotion is propose-only and hands off to the epic skill, while epic demotion is refused when open sub-issues exist and routes to epic-retrospective. The backlog skill never sets the epic label or creates epics itself.
Auto-file mode embeds an autofile-id HTML comment in each filed issue so repeated findings from QC, doc-audit, or code-review runs never create duplicate open issues. On a dedup hit it updates or comments on the existing issue instead.
Use Capture when the idea is half-formed and you only have a user story; it files quickly with a needs-grooming label and defers all heavy authoring. Use Create when the issue is ready for full specification with codebase context and epic linkage.
kagentiAnalyze GitHub PRDs to recommend the next user story with a concrete plan.
asengardeonTriage open GitHub issues and apply them as pull requests to the pipeline repository.
Garsson-ioAudit GitHub issue labels, epics, incidents, and horizons into a structured report.
Dev10x-GuruAutomate GitHub pull request creation with ticket extraction and Job Story summaries.