Agent Skills › askman-dev/coding-agent-starter › task-lifecycle

task-lifecycle

GitHub

管理任务文件在docs/tasks/各目录间的流转。根据用户指令将任务计划文件在backlog、doing、done和trash间移动，完成时触发代码地图更新，仅处理文档流程。

.agents/skills/task-lifecycle/SKILL.md askman-dev/coding-agent-starter

Trigger Scenarios

用户表示任务已开始用户表示任务已完成用户表示任务暂停或优先级降低用户表示任务被放弃或取代

Install

npx skills add askman-dev/coding-agent-starter --skill task-lifecycle -g -y

More Options

Non-standard path

npx skills add https://github.com/askman-dev/coding-agent-starter/tree/main/.agents/skills/task-lifecycle -g -y

Use without installing

npx skills use askman-dev/coding-agent-starter@task-lifecycle

指定 Agent (Claude Code)

npx skills add askman-dev/coding-agent-starter --skill task-lifecycle -a claude-code -g -y

安装 repo 全部 skill

npx skills add askman-dev/coding-agent-starter --all -g -y

预览 repo 内 skill

npx skills add askman-dev/coding-agent-starter --list

SKILL.md

Frontmatter

{
    "name": "task-lifecycle",
    "description": "Manage task file transitions across docs\/tasks\/ (backlog→doing→done→trash). Use when a user says a task has started, is complete, is on hold, or is being abandoned. Moves plan files to the correct folder and triggers code map updates on completion."
}

Task Lifecycle

Use this skill whenever a task changes state:

A task is picked up and work begins → backlog → doing
A task is finished → doing → done
A task is put on hold or deprioritized → doing → backlog
A task is abandoned or superseded → any → trash

This skill manages documentation flow only. It does not manage git branches, PRs, or worktrees.

Folder Meanings

Folder	Meaning
`docs/tasks/backlog/`	Ideas and drafts not yet started
`docs/tasks/doing/`	Actively in progress
`docs/tasks/done/`	Completed and shipped
`docs/tasks/trash/`	Abandoned or superseded

Transition Playbooks

backlog → doing

When the user selects a task to start:

Identify the plan file in docs/tasks/backlog/.
Move it to docs/tasks/doing/.
Confirm the move to the user.

doing → done

When the user says a task is complete:

Identify the plan file in docs/tasks/doing/.
Move it to docs/tasks/done/.
Invoke the code-map-maintainer skill to check whether docs/code_maps/feature_map.yaml or docs/code_maps/logic_map.yaml need updating based on what the task changed.
Remind the user: if a .worktree/ directory exists for this task, it can be manually removed.

doing → backlog

When the user puts a task on hold:

Identify the plan file in docs/tasks/doing/.
Move it to docs/tasks/backlog/.
Confirm the move to the user.

any → trash

When the user abandons or supersedes a task:

Identify the plan file in its current folder.
Move it to docs/tasks/trash/.
Confirm the move to the user.

Identifying the Right File

When the user refers to a task by name (not exact filename):

List files in the relevant folder(s).
Match by keywords in the filename.
If ambiguous, show the user the candidates and ask them to confirm before moving.

What This Skill Does NOT Do

Does not merge, close, or create PRs or branches.
Does not delete worktrees — only reminds the user to clean up manually.
Does not check whether code is actually implemented or merged before moving a file.
Does not manage tasks outside docs/tasks/.