spectra-verify

Automate code verification against change artifacts using the spectra CLI.

24|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/cashwu/Tubify --skill spectra-verify-cashwu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectra-verify
Source: https://github.com/cashwu/Tubify/tree/main/.claude/skills/spectra-verify
Command: npx skills add https://github.com/cashwu/Tubify --skill spectra-verify-cashwu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spectra, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of code implementation against change artifacts, ensuring compliance with specifications and design.

Core Features & Use Cases

  • Change Artifacts Verification: Automatically verify code against specs, tasks, and design.
  • Contextual Forking: Operates within a forked context to ensure accuracy.
  • Interactive Prompting: Allows selection of changes when multiple are present.
  • Comprehensive Reporting: Provides detailed reports on completeness, correctness, and coherence.

Quick Start

Run the spectra-verify command followed by the change name to verify the code implementation.

Frequently Asked Questions about spectra-verify

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

FAQPage Schema
How do I automate code verification against change artifacts in spec-driven development?

Automating code verification against change artifacts ensures implementation aligns with specifications, design, and tasks. This Skill uses the spectra CLI to analyze code for completeness, correctness, and coherence, providing comprehensive verification reports for developers.

Do I need the spectra CLI tool to verify code implementation against specifications?

Yes, you need the spectra CLI tool installed to verify code against specifications. This Skill operates as an automation layer that requires the spectra CLI to analyze your codebase for completeness, correctness, and coherence against your change artifacts.

How do I verify code correctness and completeness after a change implementation?

To verify code correctness and completeness after a change, run the spectra-verify command with the change name. The tool operates within a forked context to analyze code against your change artifacts and generates a detailed compliance report.

Can I select specific changes to verify when multiple change artifacts exist?

Yes, you can select specific changes when multiple change artifacts exist. The tool features interactive prompting that allows you to choose which specific change implementation you want to verify against its corresponding artifacts.

What is the best way to ensure code aligns with design specifications during development?

Using spec-driven development verification is the best way to ensure code aligns with design specifications. This approach automates the comparison of your code against change artifacts, checking for coherence and compliance with the original design.

Why does code verification fail to recognize my change artifacts during spec-driven development?

Code verification may fail if the change name provided to the spectra CLI does not match the existing artifacts, or if the spectra CLI tool is not properly installed. Ensure your change artifacts are correctly named and the required dependency is configured.