t-task-check
Validate task plan executability and consistency with a 100-point score and P0/P1/P2 fix list.
Profile →npx skills add timzaak/web-dev-skills --skill t-task-check --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` ## 目标 - 评估任务文档可执行性与一致性。 - 验证 `phase -> slot -> item` 结构。 - 给出可复查的 100 分量化结果。 - 输出 P0/P1/P2 修复清单。 - 必须按当前阶段调度对应 sub agent 做专业校验，再由主流程聚合结论。 - 本检查为可选，不作为 `/t-run` 的硬性前置；但一旦运行，报告必须严格按 rubric 给出准入风险。 - 发现必须由用户裁决的规划问题时，使用 `AskUserQuestion` 阻塞式提问，不得只写入 P0/P1/P2 后继续准入。 评分、阻塞条件、报告要求、跨轮收敛和 agent 评审边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/task-check-rubric.md` ## 事实优先级（强制） 证据优先级和争议处理统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/task-check-rubric.md` ## 使用方式 ```bash /t-task-check [feature] [--phase <backend|frontend|miniapp|flutter|web-demo|flutter-demo>] ``` | 参数 | 说明 | |---|---| | `[feature]` | 功能名（必填） | | `--phase <phase>` | 指定阶段检查；未指定时检查 `.state.json` 当前阶段 | ## 输入范围 - 设计文档：`.ai/design/[feature].md` - 决策账本：`.ai/decision-log/[feature].md`（存在时必须读取） - 需求来源：`.ai/user-stories/**/*.md`、`docs/user-stories/**/*.md`、`.ai/prd/**/*.md`、`docs/prd/**/*.md`、`.ai/tech-research/**/*.md`（按设计文档引用读取） - 状态文件：`.ai/task/[feature]/.state.json` - 阶段目录：`.ai/task/[feature]/[phase]/` - 阶段索引：`in
- 目标
- 事实优先级（强制）
- 使用方式
- 输入范围
- Schema 校验
- 执行流程
- Agent Review Contract
- 评分与问题分级
- 错误处理
- 示例
- 质量门禁
What does the t-task-check skill do?
Validate task plan executability and consistency with a 100-point score and P0/P1/P2 fix list.
How do I install it?
Run `npx skills add timzaak/web-dev-skills --skill t-task-check --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.