skills.rest
KamiJeong
KamiJeongCOMMUNITY
Explore all skills by this author →
GitHub

speckit-verify-tasks

Verify completed Spec Kit tasks against files, symbols, and diffs.

Updated May 18, 2026
Search Tags:#git diff#workflow validation#implementation audit#spec kit#task verification#phantom completion
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-verify-tasks-kamijeong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-verify-tasks
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-verify-tasks
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-verify-tasks-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks tasks marked complete in a Spec Kit workflow and helps detect phantom completions, missing implementation, and misleading checkboxes before a feature is accepted.

Core Features & Use Cases

  • Task Verification: Reviews completed items in tasks.md against referenced files, symbols, and evidence.
  • Multi-Layer Validation: Cross-checks file existence, git diffs, content matches, wiring, and semantic completeness.
  • Audit-Ready Reporting: Produces a structured verification report with verdicts, evidence gaps, and walkthrough support for flagged tasks.
  • Use Case: A product or engineering lead can validate that a supposedly finished spec task is truly implemented before merging or shipping.

Quick Start

Ask the skill to verify completed Spec Kit tasks for the active feature and generate a verification report.

Frequently Asked Questions about speckit-verify-tasks

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

FAQPage Schema
How do I verify completed tasks in a spec kit project against the actual repository state?▼

Task verification in a spec kit project involves cross-checking completed items in tasks.md against file existence, git diffs, and source symbols. This confirms implementation evidence and detects phantom completions before merging a feature.

What is phantom completion in spec-driven development and how do I detect it?▼

Phantom completion occurs when tasks.md checkboxes are marked done without actual implementation. Detect it by inspecting referenced files, git diffs, and semantic completeness to distinguish real work from misleading task status.

How do I audit git diffs for tasks marked complete in spec-driven workflows?▼

Audit git diffs by cross-checking completed task items against referenced source symbols and actual repository changes. This multi-layer validation identifies missing implementation and generates an audit-ready report with evidence gaps.

Do I need spec.md and plan.md files to verify completed tasks?▼

Yes, task verification requires project files such as spec.md, plan.md, and tasks.md. These provide the task definitions and references needed to perform source-level inspection and confirm actual repository state.

What's the best way to generate a verification report for implementation audits?▼

Generate a verification report by reviewing completed spec kit tasks against file existence, git diffs, and content matches. This produces structured verdicts and walkthrough support for flagged tasks that lack implementation evidence.

Related Skills

Explore More Software Engineering Skills→
tellbomtellbom

speckit-analyze

Identify inconsistencies, duplications, ambiguities, and underspecified items across spec.md, plan.md, and tasks.md.

Community
Intermediate
jonathanhu237jonathanhu237

openspec-verify-change

Verify change implementations against delta specs, tests, and design artifacts.

Community
Advanced
B0yZ4kr14B0yZ4kr14

speckit-verify-tasks-run

Verify completed tasks in tasks.md against real implementation evidence.

Community
Advanced
HerbertGaoHerbertGao
1

openspec-continue-change

Automates creating the next OpenSpec artifact using the openspec CLI.

Community
Advanced