review-task

Reviews task planning documents and inserts structured inline comments flagging problems against the codebase.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill review-task-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-task
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/review-task
Command: npx skills add https://github.com/mistakenot/skills --skill review-task-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Planning documents often drift from reality: file paths that don't exist, acceptance criteria without test coverage, or plan steps that contradict the proposed solution. This Skill reviews task planning docs (markdown or HTML) against the actual codebase and leaves structured inline comments so authors can fix issues before implementation begins. ## Core Features & Use Cases - Codebase-grounded verification: Checks that referenced files, types, functions, and commands actually exist and match the described signatures. - Cross-document consistency checks: Traces every acceptance criterion to test coverage and plan steps, and validates epic linkage across documents. - Structured comment threads: Inserts append-only review comments with priority levels (P1/P2/P3) in markdown comment blocks or HTML <pd-thread> elements, without modifying the author's content. - Use Case: After drafting a plan for task 042, ask for a review to catch a wrong file path in the solution tab and a missing test for one acceptance criterion before handing the task to an executor. ## Quick Start Ask the agent to review the planning docs for task 042 and leave inline comments on any problems it finds.

Frequently Asked Questions about review-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review task planning documents before implementation?▼

Provide a task ID or folder name, and the review reads every planning doc in the task folder, verifies claims against the codebase, and inserts inline comment threads flagging issues. It finishes with a summary of comment counts by priority and an overall readiness assessment.

What document formats does the planning doc review support?▼

It supports two layouts: markdown task folders with requirements.md, solution.md, context.md, and plan.md, and HTML planning docs like plan.html or epic.html built with pd-* web components. Comment syntax adapts automatically to the file extension.

Can this review code changes or pull requests?▼

No. It is explicitly scoped to planning documents, not code review of implementation changes. It uses the codebase only as ground truth to verify that the plan's claims about files, types, and commands are accurate.

Does the reviewer edit the planning documents directly?▼

No. The only edit action is inserting comment threads; the author's content is never changed. Threads are append-only, so existing comments are never edited or deleted, preserving a full decision history.

What happens when a planning doc review finds no issues?▼

It inserts a single resolved clean-review comment at a defined location so the calling agent can distinguish a successful clean review from a failed review that produced no output.