speckit-verify-tasks-run

Task verification cross-references completed Spec Kit tasks with repository files, git diffs, and content patterns to detect phantom completions. It checks file existence, scans dead code, and performs semantic assessment to ensure marked tasks have real implementation evidence.

Phantom completion detection identifies tasks marked as done that lack actual implementation evidence. It cross-references task metadata with repository structure, git diffs, and code symbols to find missing or dead work before merging or releasing a feature branch.

Checking Spec Kit tasks involves parsing task metadata and cross-referencing it with file existence, changed files, and content matching. This verification pass applies to feature branches and uncommitted work to confirm implementation evidence matches the claimed progress.

Yes, task verification is designed for feature branches and uncommitted work. It performs plan-anchored verification by cross-referencing git diffs and code symbols to ensure completed tasks have real implementation evidence before you proceed with review, merge, or release.

No specific dependencies are required. The task verification mechanism operates by parsing tasks, checking file existence, cross-referencing diffs, and scanning for dead code directly within Spec Kit projects that contain tasks, specs, and plans.

The best way to audit completed tasks is plan-anchored verification, which cross-references task metadata with repository structure and git diffs. This approach detects missing or dead work by applying content matching and semantic assessment to the implementation evidence.