task-review-checklist

A review checklist for Technical Specifications (TASK documents) that checks requirements, use cases, edge cases, compatibility, consistency, security, and documentation standards.

In plain words
What is it for?
Use it to review TASK documents and verify that acceptance criteria, error handling, project terminology, architecture constraints, and related checks are covered.
Why use it?
It helps catch missing requirements, unclear behavior, contradictions, and unhandled failures before implementation begins.

Skill for Claude CodeCodex

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 skills/matrixfounder/agentic-development/task-review-checklist
Any agent
npx skills add MatrixFounder/Agentic-development --skill task-review-checklist
Clone the repo
git clone --depth 1 https://github.com/MatrixFounder/Agentic-development

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,128 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.00014 $0.01128
Opus 5 $0.00007 $0.00564
Sonnet 5 $0.00003 $0.00226
Haiku 4.5 $0.00001 $0.00113

Measured 3d ago against content hash 89c8ef8b5681, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

task-review-checklist 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 3d ago.

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.

.agent/skills/task-review-checklist/SKILL.md · 86 lines

How it starts

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

TASK Review Checklist

1. Task Compliance

  • Requirements: All user requirements covered?
  • Scope: No unrequested features?
  • Goal: Solves the core user problem?

2. Completeness (Use Cases)

  • Structure: Name, Actors, Preconditions, Main Scenario, Alternatives, Postconditions.
  • Main Scenario: Step-by-step, clear system/actor actions.
  • Alternatives: Error handling, edge cases (empty inputs, network failures).
  • Acceptance Criteria: Specific, measurable, verifiable.

3. Compatibility

  • Terminology: Uses project terms?
  • Architecture: Respects existing constraints?
  • Integrations: correctly describes interaction with existing components?

4. Consistency

  • Internal: No contradictions between UC-01 and UC-02.
  • Naming: Same entities named identically.

5. Non-Functional

  • Performance: Metrics defined?
  • Security: Critical checks (auth, inputs)?

6. Register (documentation-standards §5.5)

  • Scan attached: artifact-formalizer/scripts/scan_register.py docs/TASK.md --sections --terms docs/ARCHITECTURE.md was run, and its DETECTORS block shows no dead detector.
  • Warns resolved: zero warn, or each survivor carries a written reason.
  • Zero read correctly: if DIAGNOSTICS reports PRESSED AGAINST THE LIMIT, the sentence_near_limit findings were judged rather than ignored.
  • Reading pass covered: every section in the --sections worklist was read for rules 3, 4 and 6, not only the sections carrying findings.

7. References (documentation-standards §4.1)

  • Resolver run: python3 .agent/skills/documentation-standards/scripts/check_positional_refs.py --all docs/TASK.md was run, and its path:line coverage line is quoted in the review — not asserted to have been produced. A checklist cannot prove a command ran; pasted output can.
  • Verdicts resolved: zero REFERENT_ABSENT and REFERENT_AMBIGUOUS, or each survivor carries a written reason. REFERENT_MOVED is repaired by re-running with --fix, never argued about — the number is derived from the referent, so no judgement is involved.
  • A coordinate carrying no referent is not a defect. It is reported as not examined and is NOT required to gain one. This review never demands a migration: most corpora carry no referents at all, and adoption is the project's decision, not the reviewer's.
  • Cross-repository coordinates pinned: a path outside this repository resolves to nothing and reports UNRESOLVABLE. It carries @<rev> naming the revision measured, which is the form §4.1 already licenses for a claim about another state.

Read the full file on GitHub · 86 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. 3d ago First seen · 86 lines · 14 tokens per session scan A 89c8ef8b5681

Subscribe to this mod's changes

task-review-checklist is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,128 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-31.

Related

Other skills, from other repositories

batch

Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.

QwenLM/qwen-code · 37 tokens

extension-creator

Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…

QwenLM/qwen-code · 96 tokens

notion

Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.

elizaOS/eliza · 69 tokens

pr-feedback

Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.

strands-agents/harness-sdk · 44 tokens

argent-native-profiler

Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.

software-mansion/argent · 37 tokens

argent-tv-interact

Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…

software-mansion/argent · 107 tokens