backlog

统一管理任务待办生命周期，整合会话 TODO、工作区清单（fix_plan.md/checklist.md）与外部 issue 跟踪器。支持分类归档、P0-P3 优先级标注、状态同步、清理降级、评论跟进和创建 issue；默认执行同步、优先级重评、清理并输出摘要报告。输入为任务请求或 issue，输出更新后的清单、同步状态与优先级摘要，适合需集中管理开发 backlog 的团队。

drumrobot

热度 33.14

最近更新 2026-09-27 23:56:59

分类：任务管理依赖：Read / Edit / Write / Grep / Bash(gh:*) / Bash(python3:*)应用场景：backlog / backlog triage / backlog sync / backlog prune ...

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add backlog

Metadata

name: backlog
description: Unified backlog lifecycle management and task tracking. Orchestrates session TODOs, workspace checklists (`fix_plan.md`, `checklist.md`), and issue trackers with vendor-agnostic lifecycle contracts. Topics — triage (classify incoming requests into session/file/issue backlogs), priority (GitHub-aligned P0-P3 urgency tagging and blocker triage), sync (external tracker status polling and resolution), prune (demote lower-priority backlog noise from active focus), lifecycle (authoring, state transitions, DoD criteria), comment (post follow-up notes/sub-findings to parent issues), create (issue and intake issue creation). Use when: "backlog", "backlog triage", "backlog sync", "backlog prune", "task lifecycle", "manage backlog", "backlog priority", "backlog cleanup", "plane backlog", "issue comment".
metadata: {"author":"es6kr","version":"0.1.0"}
depends-on: ["fix-plan","todowrite","github-flow"]
allowed-tools: ["Read","Edit","Write","Grep","Bash(gh:*)","Bash(python3:*)"]

Backlog

Unified backlog lifecycle management and orchestration across multiple storage layers (session WIP, markdown checklist files, and issue trackers).

Overview

The backlog skill provides a consistent operational interface for capturing, classifying, synchronizing, prioritizing, and maintaining backlogs across software development lifecycles.

Incoming Task / Request
  ├─ In-Session Short-Lived  ──→ /wip (Session Task API / TodoWrite)
  ├─ Workspace Markdown File ──→ /fix-plan (fix_plan.md / checklist.md)
  └─ Team-Shared External    ──→ Issue Tracker (GitHub Issues / Forge / Secondary Trackers)

Topics

Topic	Description	Guide
`prune`	Demote lower-priority items (P2/P3) and stale entries to preserve lean active focus sections	prune.md
`comment`	Post follow-up notes and nested review findings as comments on parent issues	comment.md
`create`	Create issues and intake items via API with fallback mechanisms	create.md

Default Invocation (`/backlog`)

When invoked with no arguments, the backlog skill runs the standard health and synchronization pipeline:

Sync: Poll external status for linked issues and pull requests to update resolved items.
Priority Triage: Re-evaluate urgency and blockers across active items.
Hygiene & Prune: Identify bloated or stale tasks exceeding active capacity.
Summary Report: Output an actionable breakdown of immediate priority candidates.

Configuration

Option	Default	Description
`--file=<path>`	`fix_plan.md`	Target markdown checklist path for local operations
`--role=<pm\|deep\|impl>`	(unset)	Execution role profile filter for pipeline scoping
`--secondary-sync=<skill>:<topic>`	(unset)	Abstract receiver contract for non-GitHub backlog synchronization

Cross-Workspace & Secondary Trackers

Vendor-specific and proprietary tracker integrations (e.g. Jira, Plane, internal enterprise backlogs) are decoupled from this public core skill through abstract Receiver Contracts (--secondary-sync). Private multi-repo orchestrators handle proprietary endpoints without polluting public skill schemas.