task-verification

Compare todos CLI task requirements with implementation code to detect gaps.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/sori883/myfriend --skill task-verification-sori883
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-verification
Source: https://github.com/sori883/myfriend/tree/main/.claude/skills/task-verification
Command: npx skills add https://github.com/sori883/myfriend --skill task-verification-sori883

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

todos CLI で管理しているタスクの要件(content フィールド)と実装コードを突き合わせ、仕様適合性を検証します。

Core Features & Use Cases

  • 要件と実装の突合: content に記載された要件とコードの実装を対比し、漏れや乖離を検出します。
  • ゲートチェック: タスクの完了前の検証フェーズで要件適合性を確認します。
  • レポート出力: 適合/不適合を整理した検証レポートを生成します(要件、コード、サブタスクの対応関係を示す)。

Quick Start

指定されたタスクIDの要件と実装を照合して、差分レポートを取得してください。

Frequently Asked Questions about task-verification

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

FAQPage Schema
How do I verify task requirements align with my code implementation?

Verifying task requirements align with code involves comparing the requirements stored in the todos CLI task's content field against the actual implementation to detect gaps. The process outputs a standardized report detailing matches and discrepancies.

What is a gate check for QA task completion?

A gate check for QA task completion is a verification phase confirming that a task's content-defined requirements are fully aligned with the actual code implementation before the task is marked done.

How do I check my todos CLI tasks for specification gaps?

Checking todos CLI tasks for specification gaps requires running a verification flow that identifies requirements from the content field, locates corresponding code, and generates a report showing matches and missing implementations.

Does task verification work without external dependencies?

Task verification works without external dependencies, relying solely on the todos CLI task content and the corresponding implementation code to structure the verification flow and detect requirement gaps.

What is the best way to generate a code review report for task requirements?

The best way to generate a code review report for task requirements is to structure the verification flow, identify requirements, locate corresponding code, and output a standardized report detailing matches and gaps.

When should I not use automated requirement verification?

Automated requirement verification should not be used when a task's content field lacks defined requirements, as the tool relies on comparing explicitly stated requirements against the corresponding code implementation to function.