task-spec
Skill4 starsChanged 6 months agoMITView on GitHub
Generate or append a task entry into tasks-pX.md following the task-list field standard defined in docs/claude/standards.md.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- emersonnakashima/task-spectheir own version, first seen Nov 15, 2026
- ji-hun-git/how-to-use-aitheir own version, first seen Nov 15, 2026
- hammoda711/task-spec-skilltheir own version, first seen Nov 8, 2026
- eyeix/skillstheir own version, first seen Oct 13, 2026
- MagicianDu/task-spec-studiotheir own version, first seen Jul 1, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- eyeix/skills★ 1same name
- emersonnakashima/task-spec★ 0same name
- hammoda711/task-spec-skill★ 0same name
- ji-hun-git/how-to-use-ai★ 0same name
- MagicianDu/task-spec-studio★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- acceptance-checkSkill
- bugfixSkill
- implementation-checkSkill
- release-checkSkill
- reviewSkill
- test-specSkill
- token-reportSkill
The file
Files
task-spec
按 docs/claude/standards.md#任务清单应至少包含 字段,生成单条任务条目并追加到指定 tasks-pX.md 文件。
用法
/task-spec <文件名> <任务描述>
示例:/task-spec tasks-p5.md 给 RAG 加中文分词器
字段要求
每条任务必须包含基础字段和长任务可恢复字段:
id:稳定任务编号;无现有编号时按目标任务文件的编号风格生成。- 任务名称
- 责任角色(CEO / PM / Architect / Engineer / QA / Ops / Growth)
- 输入(文件路径 / 现有结构 / 数据来源)
- 输出(被修改/新增的文件、产物)
depends_on:前置任务 ID;无依赖时写none。- 完成标准(可验证的判断条件)
read_before_start:开始或继续前必须读取的任务条目、依赖产物、相关文件、pending diff 或验收记录。execution:执行主体,取值参考main、explore、skill、manual_review、qa_acceptance。evidence:完成时填写产物、验证方式、验证结果或未验证原因;新任务可写pending。handoff:跨会话时填写当前状态、下一步、阻塞项、需重读文件和最近验证结果;新任务可写pending。
输出格式
遵循项目现行任务条目格式,并显式写入长任务字段;不得只依赖 files/context 注释承载恢复信息:
- [ ] <id> <任务名称> <!-- files: <受影响文件列表> --> <!-- context: <责任角色 / 输入 / 输出 / 完成标准> --> <!-- depends_on: <none|任务ID列表> --> <!-- read_before_start: <必读条目/文件/证据> --> <!-- execution: <main|explore|skill|manual_review|qa_acceptance> --> <!-- evidence: <pending|产物+验证+结果> --> <!-- handoff: <pending|当前状态+下一步+阻塞项+需重读文件+最近验证> --> <!-- auto|review|order|decision -->执行标注:
auto— 可由 Agent 直接小步执行review— 需要人工取舍/评审order— 必须在前置任务后顺序执行decision— 已确认的决策
执行规则
- 读取目标
tasks-pX.md现有结构,保持分组(P0/P1/P2... 或自定义分组)一致。 - 字段缺失时不得猜测,要求用户补充或显式标记"待补充"。
- 同一文件内任务编号若已存在,按现有编号风格延续。
- 写入前展示生成结果,确认后再 Edit/Write。
- 默认优先细颗粒度拆分:一条任务尽量只覆盖一个文件类型、一个流程步骤或一个可验收目标;如果任务包含多个输出、多个阶段或多个验收点,优先拆成更小任务,除非用户明确要求合并。
- 禁止把定义、实现、验证、索引、迁移混成同一条任务;若同一需求同时包含这些动作,必须拆成可独立验收的连续任务。
- 定义类任务只产出规则或格式;实现类任务只修改代码或配置;验证类任务只产出检查结论;索引类任务只维护入口列表;迁移类任务只迁移既有条目或样例。
- 若拆分后的任务之间存在先后关系,必须显式标注依赖与顺序,避免依靠任务标题或自然语言顺序推断。
- 生成依赖时必须把前置任务 ID 写入
depends_on;多个前置任务用逗号分隔,例如depends_on: LT-07, LT-08。 order、review、auto、decision只是执行或审批标注,不能替代depends_on;有先后关系时两者应同时存在。- 无前置任务必须写
depends_on: none,不得写“无依赖”“见上文”或只在context中描述。
示例任务条目
无前置依赖示例:
- [ ] LT-01 定义长任务字段标准 <!-- files: docs/claude/standards.md --> <!-- context: 责任角色=PM/Architect;输入=现有任务清单字段;输出=长任务字段说明;完成标准=standards.md 明确字段含义和必填性 --> <!-- depends_on: none --> <!-- read_before_start: tasks-p8.md LT-01 条目、docs/claude/standards.md --> <!-- execution: main --> <!-- evidence: pending --> <!-- handoff: pending --> <!-- review -->有前置依赖示例:
- [ ] LT-07 更新 task-spec 字段要求 <!-- files: .claude/skills/task-spec/SKILL.md --> <!-- context: 责任角色=PM/Engineer;输入=LT-01 到 LT-06 字段标准;输出=task-spec 支持长任务字段;完成标准=新生成任务包含可恢复字段 --> <!-- depends_on: LT-01, LT-02, LT-03, LT-04, LT-05, LT-06 --> <!-- read_before_start: tasks-p8.md LT-07 条目、docs/claude/standards.md 长任务字段规则、.claude/skills/task-spec/SKILL.md --> <!-- execution: main --> <!-- evidence: pending --> <!-- handoff: pending --> <!-- order -->验收
- 生成条目包含全部基础字段和长任务可恢复字段
- 条目格式与目标文件其他条目一致(同样的 HTML 注释结构)
- 依赖关系必须写入
depends_on,执行/审批属性写入auto、review、order或decision - 不破坏目标文件已有内容
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

