cash-verify

Cross-reference source code with project artifacts to verify implementation consistency.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cash-verify
Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-verify
Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that software implementation remains strictly aligned with project specifications, tasks, and design documentation, preventing drift and ensuring high-quality delivery.

Core Features & Use Cases

  • Artifact Verification: Automatically checks implementation completeness against tasks.md and spec requirements.
  • Consistency Checking: Validates code against design decisions and project-wide patterns.
  • Use Case: Before archiving a completed feature, run this tool to verify that all requirements from the delta specs are implemented and that no tasks remain in an incomplete state.

Quick Start

Use the cash-verify skill to validate the current implementation against the specified change artifacts.

Frequently Asked Questions about cash-verify

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

FAQPage Schema
How do I verify code implementation against project specifications and design documents?

Spec-driven verification checks implementation consistency by cross-referencing source code with project artifacts. It executes automated checks for task completion, requirement coverage, and design pattern compliance within Git-managed repositories to prevent specification drift.

Do I need a Git-managed repository to check task completion and requirement coverage?

Yes, spec-driven verification operates within Git-managed repositories to ensure adherence to defined requirements and architectural patterns. It uses a project-local CLI launcher to execute automated checks for task completion and requirement coverage against your project artifacts.

What is the best way to validate implementation completeness before archiving a feature?

The best way to validate implementation completeness is to run automated verification against delta specs and tasks. This ensures all requirements are implemented and no tasks remain incomplete, preventing architectural drift before archiving a completed feature.

How do I check if my source code follows project-wide architectural patterns?

Consistency checking validates source code against design decisions and project-wide patterns using a project-local CLI launcher. It cross-references your implementation with project artifacts to ensure strict adherence to defined architectural patterns and design documents.

When should I not use automated spec-driven verification for compliance checking?

Spec-driven verification is not suitable when project artifacts like specifications, tasks, or design documents are missing or outdated. It relies on cross-referencing source code with these project-local artifacts to execute meaningful compliance checks and validate requirement coverage.

Can I use a project-local CLI launcher to automate requirement coverage checks?

Yes, spec-driven verification uses a project-local CLI launcher to execute automated checks for requirement coverage and task completion. It cross-references source code with project artifacts to ensure implementation consistency and compliance with defined requirements.