集成

backlog

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".

它能做什么

技能文档

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
`triage`	Route incoming tasks to the appropriate persistence layer based on lifespan and collaboration scope	triage.md
`priority`	Apply P0–P3 priority tags (`[BLOCKED:P*:reason]`) and separate selfable vs external blockers	priority.md
`sync`	Poll remote and external forge states (`gh` CLI / Secondary Trackers) to reconcile completed tasks	sync.md
`prune`	Demote lower-priority items (P2/P3) and stale entries to preserve lean active focus sections	prune.md
`lifecycle`	Definition of Done (DoD), atomic marker transitions (`[ ]` → `[/]` → `[x]`), and archive rules	lifecycle.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=`	`fix_plan.md`	Target markdown checklist path for local operations
`--role=`	(unset)	Execution role profile filter for pipeline scoping
`--secondary-sync=:`	(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.

backlog-planner

Turn a feature idea, conversation context, or rough notes into researched, detailed, dependency-ordered checkbox tasks appended to the project's roadmap/backlog file — exactly the format goal-runner consumes, so a fresh unattended session can execute them. Grounds every task in the actual codebase before writing it (grep/read or Explore scouts; think-like-fable rigor if installed), puts what + done-when on the checkbox line with verified files, acceptance criteria, and a verification command in plain sub-bullets, and labels assumptions. Appends to the existing ROADMAP.md/BACKLOG.md/TODO.md; when none exists it asks once and defaults to ROADMAP.md. Use this skill whenever the user says "add this to the backlog", "add it to the roadmap", "plan these tasks", "break this down into tasks", "capture this as roadmap tasks", "turn these notes into a task list", or "/backlog-planner" — even if they don't name the skill. Not for executing tasks (goal-runner, task-executor, autopilot) — this writ

1 次安装

dev-inbox

Triage and persist work outside the explicit active objective. Use at message intake when a message contains multiple requests, an item is unrelated or deferred, the user asks to remember, track, log, or handle something later, or invokes dev-inbox. After resume or context compaction, audit requested-but-unrecorded items before continuing.

12 次安装

feature-review

Scores backlog items with RICE/WSJF/Kano and files GitHub issues for top candidates

22 次安装

Triage / Task Prioritization

按延迟成本把涌入的工作分成 P0–P3，决定先做什么、什么等、是否要打断当前任务。

44 次安装3 星标

fix-plan

fix_plan.md / checklist.md schema and lifecycle management. Topics — format ([ ]/[x]/[BLOCKED] markers, Progress/Completed sections), priority (P0-P3 BLOCKED suffix + external/selfable classification), add (Action/Why/How authoring), update (flip marker / append progress note on an existing item), upsert (dup-check → update in place or fall back to add), draft (deferred plan stub → promote via code-workflow), move ([x] → Completed summary, subtree partial completion), sync (gh pr/issue state polling → auto-check), issue-drafts (write → publish → archive → delete), model-triage (fit + dedicated section), completion-criteria (DoD + marker rules). Default (no args): move (or archive-receiver) → format → sync → priority → flowchart-sync, scoped by role-profile (--role=pm|deep|impl). Use when: "fix_plan", "checklist", "BLOCKED priority", "triage blocked", "fix-plan sync", "issue draft cleanup", "fix-plan draft", "fix-plan default", "fix-plan archive", "model triage", "completion criteria",

5 次安装

Process Keeper

Backfill development history and keep compact process logs