gentleman-programming/engram/backlog-triage
Claude Code and agent skill by gentleman-programming/engram
- community
Checking that the SKILL.md file is still in the repository.
Backlog triage protocol for Engram: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable disposition report. Trigger: Auditing open issues or PRs, triaging the backlog, reviewing contributor submissions as a maintainer, or applying triage to any GitHub repo.
Install
npx vskill@latest install gentleman-programming/engram/backlog-triageSKILL.md
The same SKILL.md was published earlier as gentleman-programming/engram/backlog-triage.
When to Use
Use this skill when:
- Running a full backlog audit on Engram (or any repo)
- Deciding merge / request-changes / close / needs-design / approve-issue
- Cleaning noise from the issue tracker
- Prioritizing what to act on next
Maintainer Philosophy (Engram)
These are the non-negotiable product values. Every triage decision is filtered through them.
| Principle | What it means in practice | |
|---|---|---|
| Zero-config | Works out of the box. No required flags, env vars, or setup beyond install. | |
| Local-first | Data lives in ~/.engram/engram.db. No cloud dependency by default. | |
| Single binary | One engram binary. No daemon, no service, no secondary processes needed. | |
| Terminal-first | CLI and TUI are the primary UX. No web dashboard, no Electron. | |
| Thin adapters | Plugin scripts (Claude, OpenCode, Gemini, Codex) are thin shims — logic lives in Go core. | |
| Issue-first | Every PR must link a status:approved issue. No approved issue → no PR. | |
| Evidence-based reviews | Request changes with specific, actionable items. No vague "needs improvement". | |
| Tight scope | Reject features that expand Engram's surface area without a compelling case. | |
| Small focused contributions | Prefer 50-line PRs solving one problem over 500-line PRs solving five. | |
| Reject vague/scope-breaking work | Close scope-creep issues and PRs that turn Engram into something else. |
Disposition Classification
Assign exactly ONE disposition to each issue or PR:
| Disposition | When to use | |
|---|---|---|
| MERGE | PR is correct, scoped, tests pass, linked approved issue. Merge immediately. | |
| REQUEST CHANGES | PR has the right idea but needs specific fixes. List each item. | |
| CLOSE | Noise, confirmed duplicate, vague/scope-breaking work, or obsolete work after maintainer review; missing approval/ownership alone requires remediation before merge. | |
| NEEDS DESIGN | Idea is valid but architectural decision required before any PR is welcome. Open discussion or design issue first. | |
| APPROVE ISSUE | Maintainer accepted proportional evidence per CONTRIBUTING.md; bugs include current-main SHA, reproduction, root cause, and regression test plan. Replace the current status with status:approved. | |
| REJECT ISSUE | Vague, duplicate, scope-breaking, or belongs in Discussions. Close with explanation. |
Operating Phases
Phase 1 — Fetch the Backlog
Phase 2 — Classify Each Item
For every issue, answer:
For every PR, answer:
Existing PRs must comply before merge; activating the gate does not require completing the whole backlog first. Reconcile approval/ownership as PRs become active or approach merge, re-run native validation after issue changes, and never assign placeholders to satisfy CI. Evidence can live in the issue; no separate design document is required by default.
Phase 3 — Infer Ideology from Maintainer Comments
Look for maintainer responses (MEMBER or OWNER association) in issue comments. Extract:
- What the maintainer approved and how they framed it
- What the maintainer redirected (Questions → Discussions, etc.)
- What the maintainer scoped down ("Best place for it: add a section in DOCS.md")
- What the maintainer welcomed vs deferred ("I'll keep this issue open to track that")
Use these patterns to calibrate your triage against the actual maintainer stance, not just the written philosophy.
Phase 4 — Prioritize
Rank items within each disposition bucket:
Quick wins (act immediately):
- Real bugs with clear reproduction steps + no linked PR yet
- PRs that are correct, scoped, and just need a label or minor fix
- Docs PRs that are accurate and unambiguous
Process blockers (fix the pipeline):
- PRs missing approval or ownership (request remediation before merge)
- PRs missing
type:*label (request changes) - Issues with
status:needs-reviewthat have been waiting > 7 days
Real bugs (high priority issues):
- Reproducible crashes, data loss, or broken core workflows
- Issues with multiple confirming comments from different users
Architectural proposals (schedule separately):
- Issues tagged NEEDS DESIGN
- Proposals that affect the binary's interface, sync protocol, or plugin contract
Noise (close immediately):
- Issues without reproduction steps
- Feature requests that expand scope without evidence of demand
- Questions that belong in Discussions
- Vague reports ("it doesn't work")
Phase 5 — Produce the Report
Output a structured triage report:
Quick-Action Commands
Reusable Prompt Template
Copy this block to apply the triage workflow in any repository:
Tradeoffs and Assumptions
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/backlog-triage/SKILL.md
Popularity
- Repository stars
- 7,690
- Repository forks
- 809
- 7-day trend score
- 42
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/gentleman-programming/engram/backlog-triage)