check-task

A command that reports the status of a software task by reading its task file and progress documents.

In plain words
What is it for?
Use it with a task ID to check progress, inspect available analysis or implementation reports, and see the suggested next step.
Why use it?
It shows which workflow steps are finished, in progress, waiting for review, or blocked, along with the responsible AI and related files.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/modelengine-group/fit-framework/check-task
Clone the repo
git clone --depth 1 https://github.com/ModelEngine-Group/fit-framework

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,325 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.01325
Opus 5 $0.00005 $0.00662
Sonnet 5 $0.00002 $0.00265
Haiku 4.5 $0.00001 $0.00133

Measured yesterday against content hash 8ecc21fdd0f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-task scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/check-task.md · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Task Status Command

功能说明

查看指定任务的当前状态、进度和上下文文件。

执行流程

1. 读取任务文件

读取 .ai-workspace/active/{task-id}/task.md(如果任务已完成,也检查 completed/ 目录)

2. 检查上下文文件

检查以下文件是否存在:

  • analysis.md - 需求分析
  • plan.md - 技术方案
  • implementation.md - 实现报告
  • review.md - 审查报告

3. 分析当前状态

根据任务文件和上下文文件,确定:

  • 当前执行到哪个步骤
  • 哪些步骤已完成
  • 哪些步骤待执行
  • 当前负责的 AI
  • 是否等待人工审查

4. 输出状态报告

输出格式化的状态信息:

📋 任务状态报告

**基本信息**:
- 任务ID: {task-id}
- 任务标题: {title}
- 任务类型: {type}
- 相关Issue: #{issue-number}
- 创建时间: {created_at}
- 更新时间: {updated_at}

**当前状态**:
- 工作流: {workflow}
- 当前步骤: {current_step}
- 执行者: {assigned_to}
- 状态: {status}

**工作流进度**:
✅ 需求分析 (完成于 {date})
✅ 技术方案设计 (完成于 {date})
⏳ 代码实现 (进行中)
⏸️  代码审查 (待开始)
⏸️  问题修复 (待开始)

**上下文文件**:
✅ analysis.md (2.5 KB)
✅ plan.md (8.3 KB)
⏳ implementation.md (进行中)
❌ review.md (未创建)

**文件路径**:
- 任务文件: .ai-workspace/active/{task-id}/task.md
- 上下文目录: .ai-workspace/active/{task-id}/

**下一步建议**:
{根据当前状态给出建议}

参数说明

  • <task-id>: 任务ID,格式为 TASK-{yyyyMMdd-HHmmss}(必需)

使用示例

# 查看任务状态
/check-task TASK-20251227-104654

# 也可以简写
/check-task TASK-20251227-104654

状态说明

任务状态

  • active - 进行中
  • blocked - 被阻塞
  • completed - 已完成

步骤状态

  • ✅ 已完成
  • ⏳ 进行中
  • ⏸️ 待开始
  • ❌ 失败/阻塞

下一步建议

根据当前状态自动生成建议:

如果在需求分析阶段

继续完成需求分析,完成后使用:
- Claude Code / OpenCode: /plan-task {task-id}
- Gemini CLI: /fit:plan-task {task-id}
- Codex CLI: /prompts:fit-plan-task {task-id}

如果需求分析完成,等待人工审查

⚠️  等待人工审查需求分析
审查通过后使用:
- Claude Code / OpenCode: /plan-task {task-id}
- Gemini CLI: /fit:plan-task {task-id}
- Codex CLI: /prompts:fit-plan-task {task-id}

如果在技术方案设计阶段

继续完成技术方案设计,完成后等待人工审查

如果方案设计完成,等待人工审查

⚠️  等待人工审查技术方案
审查通过后使用:
- Claude Code / OpenCode: /implement-task {task-id}
- Gemini CLI: /fit:implement-task {task-id}
- Codex CLI: /prompts:fit-implement-task {task-id}

如果在代码实现阶段

继续完成代码实现,完成后使用:
- Claude Code / OpenCode: /review-task {task-id}
- Gemini CLI: /fit:review-task {task-id}
- Codex CLI: /prompts:fit-review-task {task-id}

Read the full file on GitHub · 200 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 200 lines · 11 tokens per session scan A 8ecc21fdd0f5

Subscribe to this mod's changes

check-task is a command published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,325 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.