paulund/ops-backlog-health
ops-backlog-health/SKILL.md
Use when the user wants a periodic health pass over the backlog — close stale blockers, surface drifted-priority items, flag long-running in-progress issues, and unblock issues whose blockers were closed. Designed to run on a schedule (e.g. weekly) alongside /ops-triage. Trigger phrases - "/ops-backlog-health", "backlog health pass", "scrub the backlog".
$ install --global
skillsauthnpx skillsauth add paulund/skills ops-backlog-healthInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 10, 2026, 5:07 AM154.2s1 file scanned
SKILL.md
- name:
- ops-backlog-health
- description:
- Use when the user wants a periodic health pass over the backlog — close stale blockers, surface drifted-priority items, flag long-running in-progress issues, and unblock issues whose blockers were closed. Designed to run on a schedule (e.g. weekly) alongside /ops-triage. Trigger phrases - "/ops-backlog-health", "backlog health pass", "scrub the backlog".
- category:
- ops
Backlog Health
Periodic, non-interactive scrub of the backlog. Surfaces drift, closes resolved blockers, and reports a one-screen summary. Does NOT triage individual issues — that's /ops-triage.
Workflow
Pass 1 — Close stale blockers
For every open issue with the blocked label:
- Parse the issue body for
## Blocked by #Nreferences. - Run
gh issue view <N> --json statefor each blocker. - If all blockers are CLOSED, remove the
blockedlabel and post a comment:
gh issue comment <N> --body "$(cat <<'EOF'
> *Backlog health pass: blockers resolved.*
All referenced blockers are closed. Removing `blocked` label.
EOF
)"
gh issue edit <N> --remove-label blocked
If only some are closed, leave the label and surface the partial-progress in the report.
Pass 2 — In-progress drift
gh issue list --label "in-progress" --state open --json number,title,updatedAt,assignees
For each: if updatedAt is older than 14 days and there's no associated open PR (gh pr list --search "in:body #<N>" returns empty), flag it as a drift candidate. Don't auto-action — surface in the report.
Pass 3 — Stale planned items
gh issue list --label "planned" --state open --json number,title,createdAt,labels
For each: if createdAt is older than 60 days and the issue is afk, surface it. The reporter or backlog-owner needs to decide if it still makes sense.
Pass 4 — Priority drift
For issues with p1 older than 7 days, surface them — p1 items should not linger.
Pass 5 — Report
Post a single GitHub Discussion or pinned issue comment summarising the pass:
## Backlog Health — <ISO date>
**Closed-blockers unblocked:** <count> (#N1, #N2, …)
**Drift candidates (in-progress >14d, no PR):**
- #<N>: <title> — last updated <date>
**Stale planned (>60d, afk):**
- #<N>: <title>
**p1 lingering (>7d):**
- #<N>: <title>
If no items in any bucket, post a one-line "Backlog clean — no findings" message.
Constraints
MUST DO
- Operate read-only on individual issues except for the explicit
blockedremoval in Pass 1. - Surface drift; never auto-close planned or in-progress issues without human direction.
- Include the AI disclaimer (
> *This was generated by AI during a backlog health pass.*) on any GitHub-visible output.
MUST NOT DO
- Triage individual issues — that's
/ops-triage. - Close issues automatically (only label changes are allowed).
- Re-prioritise issues automatically.
- Run interactively — this skill is designed for scheduled / unattended runs.
Related Skills
paulund/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any logic, fixing any bug, or changing any behaviour. Use when you need to prove code works, when a bug report arrives, or when modifying existing functionality. Do NOT use for config changes, data migrations, or dependency updates.
3SKILL.mdUpdated Jul 1, 2026
paulund/spec-driven-development
development
VerifiedTrustedCommunity
Use when starting a new feature, when requirements are unclear, when asked to write code without a clear spec, or before any non-trivial implementation. Do NOT use for trivial bug fixes or one-line changes.
3SKILL.mdUpdated Jul 1, 2026
paulund/source-driven-development
development
VerifiedTrustedCommunity
Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters. Detects the stack from dependency files, fetches official documentation, implements following documented patterns, and cites sources for every framework-specific decision.
3SKILL.mdUpdated Jul 1, 2026
paulund/shipping-and-launch
development
VerifiedTrustedCommunity
Use when preparing to ship a feature, release, or deployment. Use before merging to main, creating a release, or deploying to production. Do NOT use for CI-only changes or internal refactors that don't reach production.
3SKILL.mdUpdated Jul 1, 2026