Agent skill

Task Manager

by 312362115 in 312362115/claude

需求全生命周期管理:收集、排序、清理、跟踪、关闭. An agent skill from 312362115/claude.

MITAuto-check passedProductivity & Automation

Install Task Manager

skills CLI
$ npx skills add 312362115/claude --skill task-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 312362115/claude task-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/312362115/claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/task-manager .claude/skills/task-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
task-manager
GitHub stars
107
Token cost
~1.7k tokens
SKILL.md length
322 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

需求全生命周期管理:收集、排序、清理、跟踪、关闭. An agent skill from 312362115/claude.

  • Works in 3 steps: 先按紧急度分层(P0-P3) → 同层内按价值/成本比排序:价值高且成本低的排前面 → 有依赖关系的考虑顺序:A 依赖 B,则 B 排在 A 前面
  • Tasks that involve Task management
  • SKILL.md covers 核心职责, 操作 1:新增需求, 操作 2:梳理 backlog and 操作 3:优先级排序, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Task Manager is an agent skill from 312362115/claude. 需求全生命周期管理:收集、排序、清理、跟踪、关闭。 管理 docs/backlog/ 目录下的需求文件和 INDEX.md 索引。 核心职责:需求状态变更是整个工作流的驱动力—— open(收集)→ 启动 task-start → 执行 → done(关闭时触发复盘 + 经验沉淀 + 文档更新)。 触发词:梳理需求、排优先级、backlog、需求管理、看看还有什么要做的、需求池、 这个需求做完了、标记完成、关闭需求。 触发场景:开新迭代前梳理需求、积累了一堆需求要排序、定期清理过期需求、需求完成关闭时。 本 skill 管"做不做、做哪个、做完了吗",task-start 管"怎么做",plan 管"做到哪了"。

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Task management. The licence is MIT.

When your agent uses it

  • Tasks that involve Task management

Example prompts

  • “做不做、做哪个、做完了吗”
  • “,plan 管”
  • “/task-manager”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. 先按紧急度分层(P0-P3)
  2. 同层内按价值/成本比排序:价值高且成本低的排前面
  3. 有依赖关系的考虑顺序:A 依赖 B,则 B 排在 A 前面

What it can do on your machine

Read from SKILL.md and the folder at commit 2d4fa49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Task Manager loads about 1.7k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 322 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 312362115/claude at commit 2d4fa49, republished under its MIT licence (© 312362115). 322 words, ~1,671 tokens.

Download SKILL.mdSave it as .claude/skills/task-manager/SKILL.md (or your agent's skills folder).
name
task-manager
description
需求全生命周期管理:收集、排序、清理、跟踪、关闭。 管理 docs/backlog/ 目录下的需求文件和 INDEX.md 索引。 核心职责:需求状态变更是整个工作流的驱动力—— open(收集)→ 启动 task-start → 执行 → done(关闭时触发复盘 + 经验沉淀 + 文档更新)。 触发词:梳理需求、排优先级、backlog、需求管理、看看还有什么要做的、需求池、 这个需求做完了、标记完成、关闭需求。 触发场景:开新迭代前梳理需求、积累了一堆需求要排序、定期清理过期需求、需求完成关闭时。 本 skill 管"做不做、做哪个、做完了吗",task-start 管"怎么做",plan 管"做到哪了"。
version
1.1.0
last_updated
2026-04-08
repository
https://github.com/312362115/claude

需求管理(Task Manager)

backlog 不梳理就是垃圾堆。定期梳理,该做的做、该删的删、该提的提。


核心职责

需求管理 = 收集 + 排序 + 清理 + 跟踪
职责做什么
收集新需求写入 docs/backlog/,更新 INDEX
排序定期重新评估优先级(P0-P3)
清理过期/无效需求标记 dropped,保持 backlog 清洁
跟踪需求状态流转:open → in-progress → done / dropped
需求状态定义
open ──→ in-progress ──→ done
  │                        │
  └──→ dropped             └─ 触发复盘 + 经验沉淀
状态含义触发时机驱动行为
open已收集,待排期需求创建时无
in-progress开发中task-start 启动时无(方便跨会话跟踪进度)
done彻底完成用户确认关闭触发复盘 + Ingest
dropped放弃需求失效/优先级归零记录 drop 原因

in-progress 的价值:跨会话时能快速定位"上次做到哪了"——看 backlog 中哪些是 in-progress,再看对应的 plan 进度。


操作 1:新增需求

markdown
# 文件:docs/backlog/YYYY-MM-DD-<主题>.md

---
priority: P2
status: open
spec: (关联方案,如有)
plan: (关联计划,如有)
---

# <需求标题>

## 背景
为什么要做这个?

## 描述
具体要做什么?

## 验收标准
做到什么程度算完?

创建后更新 docs/backlog/INDEX.md,按优先级放到对应分组。


操作 2:梳理 backlog

触发时机
  • 用户主动要求梳理
  • 开新迭代/冲刺前
  • backlog 超过 15 个 open 需求时
梳理流程
1. 读取 docs/backlog/INDEX.md,了解全貌
2. 逐条检查 open 状态的需求:
   │
   ├─ 还有价值吗?
   │   └─ NO → 标记 dropped,说明原因
   │
   ├─ 优先级还对吗?
   │   └─ 调整 priority 和 INDEX 位置
   │
   ├─ 描述还准确吗?
   │   └─ 更新描述/验收标准
   │
   └─ 有没有已完成但没标记的?
       └─ 标记 done,更新 INDEX
3. 输出梳理结论
梳理结论格式
markdown
## Backlog 梳理结论 — YYYY-MM-DD

### 概况
- 总计:X 条需求
- Open:X 条 | Done:X 条 | Dropped:X 条

### 本次调整
- P1 → P0:[需求名] — 原因
- P2 → dropped:[需求名] — 原因
- 新增:[需求名] — P2

### 建议下一步做
1. [需求名](链接) — P0,理由
2. [需求名](链接) — P1,理由

操作 3:优先级排序

优先级定义
级别含义判断标准
P0紧急阻塞其他工作、线上问题、截止日期临近
P1重要核心功能、用户高频需求、有明确截止时间
P2普通有价值但不紧急、优化类需求
P3低优锦上添花、远期规划、灵感记录
排序方法

当需要在多个需求间排优先级时:

  1. 先按紧急度分层(P0-P3)
  2. 同层内按价值/成本比排序:价值高且成本低的排前面
  3. 有依赖关系的考虑顺序:A 依赖 B,则 B 排在 A 前面

操作 4:状态变更

变更操作
open → in-progress更新 backlog 文件 status + INDEX.md 中标注 [~](开发中)
in-progress → done触发关闭流程(见下方)
open/in-progress → dropped更新 backlog 文件 status + INDEX.md 中加 ~~删除线~~ + 写明 drop 原因
优先级调整更新 backlog 文件 priority + INDEX.md 中移动到对应分组
open → in-progress

task-start 启动需求时,自动更新对应 backlog 状态:

1. 更新 backlog 文件 frontmatter: status: in-progress
2. 更新 INDEX.md: [ ] → [~]

[~] 表示开发中,和 [ ](待做)、[x](完成)区分。

需求关闭流程(open → done)

需求标 done 是整个工作流最重要的节点——这是复盘和经验沉淀的唯一触发点。 "编码完成"不等于"需求完成"。需求完成 = 用户确认这个需求彻底搞定了。 标 done 时必须提交代码:backlog 状态更新、复盘文档等变更不能积攒,随标 done 一起 commit。

用户说"这个需求做完了" / "标记完成" / "关闭这个需求"
  │
  ├─ Step 1: 更新 backlog 文件 status → done
  ├─ Step 2: 更新 INDEX.md 中 [ ] → [x]
  │
  ├─ Step 3: 复盘判断
  │   │
  │   ├─ 小需求(≤2 文件,过程顺利,无返工)?
  │   │   └─ 跳过复盘
  │   │
  │   ├─ 中等需求(过程中有波折但不大)?
  │   │   └─ 轻量复盘:回答 3 个问题
  │   │
  │   └─ 大需求 / 过程曲折 / 方向调整 / 反复修改?
  │       └─ 完整复盘:四维回顾
  │
  ├─ Step 4: 复盘产出写入 docs/decisions/YYYY-MM-DD-<主题>.md
  ├─ Step 5: 记忆管理(详见下方"记忆写入规则")
  ├─ Step 6: 触发 docs-management.Ingest(更新相关 spec/plan 状态标注)
  ├─ Step 6.1: 复盘中提到环境/工具链的坑?→ 提醒补到 guides/
  ├─ Step 6.2: 复盘中提到线上问题/部署问题?→ 提醒补到 runbooks/
  ├─ Step 7: 更新 docs/decisions/INDEX.md(如果存在)
  └─ Step 8: 提交代码 — 将本次需求的所有变更(含 backlog 状态、复盘文档)一起 commit,不积攒

强制完整复盘信号(出现以下任一,不管需求大小):

  • 需求过程中出现了方向调整或重大返工
  • 方案设计和实际执行有显著偏差
  • 发现了之前不知道的坑或隐含知识
  • 用户明确要求复盘
轻量复盘(3 个问题)
markdown
# 复盘:[需求名称] — YYYY-MM-DD

1. **方案和实际的偏差在哪?**
   - [偏差描述,没有偏差就写"无"]

2. **哪里返工了、为什么?**
   - [返工原因,没有返工就写"无"]

3. **下次怎么避免?**
   - [可复用的经验]
完整复盘(四维回顾)
markdown
# 复盘:[需求名称] — YYYY-MM-DD

## 需求概述
- 目标:[一句话描述]
- 结果:[完成情况]
- 过程顺利度:1-5 星

## 做得好的(保持)
- ...

## 做得不够好的(优化)
- ...(附原因分析)

## 通用能力沉淀
- ...

## 行动项
- [ ] ...
经验沉淀路径

docs/decisions/ 是真相源,memory 只是跨会话索引。不允许只存 memory 不写文档。

步骤存储位置性质
复盘全文docs/decisions/YYYY-MM-DD-<主题>.md真相源,随 git 提交
关键经验memory(feedback/project 类型)跨会话索引
通用规范CLAUDE.md经验提升为规范
记忆写入规则(Step 5 详细说明)

memory 是"下次对话的备忘录"——只存跨会话有用的信息,不存能从代码/git/docs 推导出的东西。

什么时候写 memory:

触发场景写什么类型示例
复盘中发现了不显然的坑feedback"Prisma migrate 在 SQLite 下不支持 ALTER COLUMN,需要重建表"
复盘中总结了可复用的做法feedback"大表加索引用 CONCURRENTLY,否则锁表"
用户纠正了你的做法feedback"不要在这个项目用 mock 测试,上次踩过坑"
用户确认了一个非显然的方案feedback"单 PR 打包重构是对的,拆太细反而是 churn"
了解到项目的阶段性目标/约束project"Q2 前必须完成合规改造,scope 优先合规"
了解到外部资源的位置reference"性能监控看 Grafana xxx 面板"

写入判断三连问:

  1. 下次对话还需要这个信息吗? → 不需要则不写
  2. 能从代码/git log/docs 推导出来吗? → 能推导则不写
  3. 会在 2 周内过期吗? → 会过期则写 project 类型(方便后续清理)

不写的:代码结构、文件路径、函数签名、具体的 bug 修复方案——这些从代码和 git 就能看到。

记忆清理规则

记忆不清理就是垃圾堆,和 backlog 一样。

清理触发时机:

  1. docs-management Lint 时:顺带检查 memory,在健康检查报告中加一节"记忆巡检"
  2. 对话开始时读到过期 memory:发现 memory 内容和当前代码/项目状态不符,当场更新或删除
  3. memory 条目超过 20 条时:主动建议用户清理

清理判断标准:

情况操作
project 类型超过 1 个月未更新检查是否仍然有效,失效则删除
feedback 类型描述的代码/模块已重构或删除删除
两条 memory 内容重复或矛盾合并或删除旧的
memory 中引用的文件/函数已不存在删除
内容已被沉淀到 CLAUDE.md 或 docs/删除 memory(docs 已是真相源)

清理操作:删除 memory 文件 + 更新 MEMORY.md 索引,和写入一样是两步。


INDEX.md 格式

markdown
# Backlog Index

## P0 — 紧急
<!-- 当前无 P0 -->

## P1 — 重要
- [~] [开发中的需求](文件名.md) — 一句话描述
- [ ] [待做需求](文件名.md) — 一句话描述
- [x] [已完成需求](文件名.md) — 一句话描述

## P2 — 普通
- [ ] [需求标题](文件名.md) — 一句话描述

## P3 — 低优
- [ ] [需求标题](文件名.md) — 一句话描述
- ~~[已放弃需求](文件名.md) — 一句话描述~~
  • [ ] = open(待做)
  • [~] = in-progress(开发中)
  • [x] = done(完成)
  • ~~删除线~~ = dropped(放弃)

与其他 skill 的关系

需求状态变更是整个工作流的驱动力。

task-manager(本 skill)
  │
  ├─ open → 收集需求、排优先级
  │   ↓ 决定做某个需求
  │
  ├─ task-start → 对焦 + 方案
  │   ↓
  │ task-execute → 编码 + 进度管理
  │   ↓
  │ task-finish → 每次提交前自检
  │   ↓
  │ (手动测试、bug 修复、调整...可能反复多轮)
  │   ↓
  ├─ done → 需求彻底完成
  │   ├─ 复盘 → docs/decisions/(经验沉淀)
  │   ├─ Ingest → docs-management(更新相关文档)
  │   └─ memory → 跨会话索引
  │
  └─ dropped → 需求放弃,记录原因
经验闭环
task-start(检索 decisions/ 历史经验)→ 执行 → task-manager 标 done(产出新经验)
      ↑                                                    │
      └──────────────── docs/decisions/ ←──────────────────┘

© 312362115, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/task-manager of 312362115/claude.

Open the folder on GitHubat commit 2d4fa49

Compare with similar skills

Task Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Task Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Task Manager this skill312362115/claude107—~1.7kAutomated safety check: PassMIT
Superset Agent Standupsuperset-sh/superset15k—~712Automated safety check: PassCustom licence
AgentRQ Workspace Agentagentrq/agentrq1.1k—~1.9kAutomated safety check: PassAGPL-3.0
Markdown Task Managerioniks/MarkdownTaskManager535—~2.2kAutomated safety check: PassMPL-2.0
Dingtalk TodoDingTalk-Real-AI/dingtalk-workspace-cli3.2k1 repos~1.9kAutomated safety check: PassApache-2.0
Pi Messenger Crewnicobailon/pi-messenger720—~3.7kAutomated safety check: PassNone

Similar skills

  • Superset Agent Standup

    superset-sh/superset

    Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.

    15k GitHub stars~712 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Guides a workspace agent through executing assigned tasks, replying to a remote human operator, and creating sub-tasks, memory and events inside an AgentRQ workspace.

    1.1k GitHub stars~1.9k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Markdown Task Manager

    ioniks/MarkdownTaskManager

    A skill your agent uses when managing tasks, the system is a Kanban task manager based on local Markdown files (kanban.md and archive.md).

    535 GitHub stars~2.2k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed
  • Dingtalk Todo

    DingTalk-Real-AI/dingtalk-workspace-cli

    钉钉待办 / TODO。Use when 用户说 创建待办/TODO/任务提醒/指派任务/标记完成/查待办/紧急待办/循环待办/批量建待办/逾期待办。不做日报周报(走 dingtalk-misc)、审批(走 dingtalk-misc)、日程(走 dingtalk-calendar)。命令前缀:dws todo。

    3.2k GitHub starsUsed in 1 repo~1.9k tokens
    Productivity & AutomationAuto-check passed
  • Pi Messenger Crew

    nicobailon/pi-messenger

    Orchestrator reference for pi-messenger Crew planning, task management, configuration, and agent coordination.

    720 GitHub stars~3.7k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Codekanban CLI

    fy0/CodeKanban

    Operate CodeKanban workflows, terminal sessions, and web sessions through the installable codekanban-cli command.

    225 GitHub stars~2.7k tokensUpdated 4 days ago
    Productivity & AutomationAuto-check passed

More from 312362115/claude

All 20 skills in this repo
  • Diagram

    312362115/claude

    专业图表生成技能:根据需求自动选择合适的图表类型,生成符合设计规范的 PNG 图表. An agent skill from 312362115/claude.

    107 GitHub stars~2.7k tokensUpdated 4 mo ago
    Auto-check passed
  • Deep Research

    312362115/claude

    深度调研技能:对任意命题进行系统性调研并输出专业研究报告. An agent skill from 312362115/claude.

    107 GitHub stars~6.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Preview Md

    312362115/claude

    MD 文件浏览器预览:GitHub 风格渲染 + 左侧自动目录. An agent skill from 312362115/claude.

    107 GitHub stars~636 tokensUpdated 4 mo ago
    Auto-check passed
  • Writing

    312362115/claude

    通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料. An agent skill from 312362115/claude.

    107 GitHub stars~1.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Code Walkthrough

    312362115/claude

    代码导读技能:帮助快速理解不熟悉的项目或模块,建立心智模型. An agent skill from 312362115/claude.

    107 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check: notes
  • DB Review

    312362115/claude

    数据库代码审查 + Migration 安全检查. An agent skill from 312362115/claude.

    107 GitHub stars~1.8k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Task Manager

What does Task Manager do?

需求全生命周期管理:收集、排序、清理、跟踪、关闭. An agent skill from 312362115/claude. Task Manager is an agent skill from 312362115/claude.

When should I use Task Manager?

Task Manager fits situations like: tasks that involve Task management.

How do I install Task Manager in Claude Code?

Run `npx skills add 312362115/claude --skill task-manager -a claude-code`. Or copy the skill folder (skills/task-manager in 312362115/claude) into .claude/skills/task-manager in your project. Claude Code loads it when a task matches its description.

How do I install Task Manager in Codex?

Run `npx skills add 312362115/claude --skill task-manager -a codex`. Or copy the skill folder (skills/task-manager in 312362115/claude) into .agents/skills/task-manager in your project. Codex loads it when a task matches its description.

Can I use Task Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 312362115/claude --skill task-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/task-manager, .gemini/skills/task-manager, .github/skills/task-manager and .opencode/skills/task-manager in your project.

What does Task Manager need to run?

SKILL.md names no scripts, command-line tools or credentials: Task Manager is instructions for the agent only.

Does Task Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Task Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Task Manager use?

Task Manager is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Task Manager use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Task Manager?

Skills that share tags, products or a category with Task Manager: Superset Agent Standup (superset-sh/superset, 15k stars), AgentRQ Workspace Agent (agentrq/agentrq, 1.1k stars), Markdown Task Manager (ioniks/MarkdownTaskManager, 535 stars) and Dingtalk Todo (DingTalk-Real-AI/dingtalk-workspace-cli, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Task Manager?

312362115 (a GitHub user) maintains it in 312362115/claude, which has 107 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on May 14, 2026.

Source: 312362115/claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.