القائمة
Create, triage, and manage GitHub issues per PPDS backlog conventions. Use when creating issues, grooming the backlog, reviewing what to work on next, or filing bugs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Cut a PPDS release — CHANGELOG refresh, version bump, tag push sequence, CI monitoring, post-publish verification. Use when preparing a new prerelease or stable release across CLI, TUI, MCP, Extension, and NuGet libraries.
Triage and merge open dependabot PRs per docs/MERGE-POLICY.md — classify each PR (auto-merge / verify-then-merge / manual review), enable auto-merge for safe ones, run targeted test suites for risky ones, and surface anything needing human judgment. Use when there's a backlog of dependabot PRs, after a quiet period, or as a routine drain.
AI self-verification of implemented work across surfaces (extension, CLI, MCP, TUI, workflow). Use after implementation to verify code works in its runtime environment.
Brainstorm ideas into specs and plans through collaborative dialogue. Use when starting a new feature, exploring an idea, or designing a system — before any implementation.
Gates
Execute a checked-in implementation plan end-to-end using parallel agents. Use when a spec and plan exist in .plans/ and you're ready to build.
| name | backlog |
| description | Create, triage, and manage GitHub issues per PPDS backlog conventions. Use when creating issues, grooming the backlog, reviewing what to work on next, or filing bugs. |
Manage GitHub issues using the label taxonomy, milestone conventions, and triage rules defined in docs/BACKLOG.md.
Read docs/BACKLOG.md at the start of every backlog operation - it is the source of truth for labels, milestones, and rules.
Read REFERENCE.md §1 "Label taxonomy" before classifying any issue.
/backlog create <description> - create a new issue/backlog triage - triage untriaged inbox/backlog review - review backlog for promotion/backlog validate - verify open issues are still valid/backlog (no args) - show backlog summarycat docs/BACKLOG.md
type: label (bug/enhancement/docs/performance/refactor)area: label (auth/cli/data/extension/plugins/tui)epic: label appliespriority: label if not obviousgh issue create --title "<title>" --body "<body>" --label "type:<type>,area:<area>" --milestone "<milestone>"
If no milestone, add status:backlog. Every issue must have at minimum one type: + one area: + either a milestone or status: label.
gh issue list --state open --limit 200 --json number,title,labels,milestone --jq '[.[] | select(.milestone == null) | select(.labels | map(.name) | any(startswith("status:")) | not)]'
Read REFERENCE.md §2 "Mandatory verification" for the per-issue checklist before presenting any issue to the user. Read REFERENCE.md §3 "Triage decision rules" for the categorization heuristic.
Surface ready-to-promote issues from status:backlog based on completion criteria + dependency satisfaction. See REFERENCE.md §4 "Promotion rules".
For each open issue, verify the symptom still reproduces and the area label is still accurate. Close stale duplicates. See REFERENCE.md §5 "Validation checklist".
.claude/skills/backlog/REFERENCE.md - taxonomy, conflict-resolution examples, and the never-do list.docs/BACKLOG.md - canonical labels and milestones.