backlog

面向软件开发流程的 backlog 管理 Skill，覆盖会话 TODO、工作区 markdown 清单与外部 issue tracker 三层存储：提供分流、优先级标注、状态同步、清理降级、issue 与评论创建以及会话记录，并附 Python 脚本对接 Plane API；默认调用会运行同步与分诊管线并输出摘要报告。

drumrobot

热度 77.54

最近更新 2026-10-18 14:07:32

分类：协作依赖：代码执行 / 读写文件 / 第三方 API应用场景：任务管理 / 工作流 / 报告撰写 / 笔记整理

安装技能

复制下面的话术发给你的 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), record (session completed work and next-session candidates). Use when: "backlog", "backlog triage", "backlog sync", "backlog prune", "task lifecycle", "manage backlog", "backlog priority", "backlog cleanup", "plane backlog", "issue comment", "backlog record".
metadata: {"author":"es6kr","version":"0.2.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
`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
`prune`	Demote lower-priority items (P2/P3) and stale entries to preserve lean active focus sections	prune.md
`record`	Record this session's completed work + register next-session candidates (session/file/issue routing)	record.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.