t-task
Convert technical design documents into executable phased task plans with ordered work breakdown.
Profile →npx skills add timzaak/web-dev-skills --skill t-task --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 任务规划生成 运行时边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 需求来源边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/requirement-source-contract.md` 决策连续性和用户决策暴露统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/decision-continuity-contract.md` 任务拆分必须服务于边界清楚、验证闭环明确的执行；如果设计文档、guide 或 protocol 冲突，停止并说明冲突。 影响规划方向的缺口必须通过 `AskUserQuestion` 解决，不得把问题写成 P0/P1、假设或 handoff 后继续生成任务。 ## Input Contract 上游输入（来自 `/t-design` 产出）： - `.ai/design/[feature].md` — 技术设计文档（必须存在） - 必须包含：目标、范围、API 接口设计、数据库设计、测试策略 - 应包含：现有实现分析、用户故事/PRD/技术预研引用、文件影响范围 - 纯技术方案设计可只包含技术预研引用，但必须声明不涉及业务逻辑、产品规则、用户可见流程或验收目标变动 - `.ai/decision-log/[feature].md` — 跨阶段决策账本（存在时必须读取；本阶段不得采用 Superseded Decision） 可选输入： - `.ai/task/[feature]/.state.json` — 已有任务状态（增量生成时） - `docs/prd/**/*.md` — PRD 文档 - `.ai/user-stories/**/*.md` — draft 用户故事 - `docs/user-stories/**/*.md` — 已发布用户故事 - `.ai/tech-research/**/*.md` — 技术预研报告 - `${CLAUDE_PLUGIN_ROOT}/guides/` — 开发规范 ## Output Contract 下游产出： - `.ai/task/[feature]/.state.json` — 任务状态文件，包含 phase/slot/item 层级状态 - `.ai/task/[feature]/<phase>/index.md` — 阶段总览，包含当前 phase 的 Decision Trace - `.ai/task/[feature]/<phase>/<slot>.md` — Slot manifest（导航与执行顺序） - `.ai/task/[feature]/<phase>/<slot>/<ITEM-ID>-*.md` — 可执行的 item
- Input Contract
- Output Contract
- Purpose
- Args
- Preconditions
- Output Layout
- Generation Flow
- Agent Dispatch Mapping
- Slot Manifest Contract
- Generated Document Style
- Agent Output Contract
- Item Contract And Splitting
- Forbidden
- Failure
What does the t-task skill do?
Convert technical design documents into executable phased task plans with ordered work breakdown.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-task --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From timzaak/web-dev-skills, a repository with 55 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.