validating-specs

Name: validating-specs
Availability: InStock
Author: davidabeyer

Validate task specification claims against the current codebase.

13|1|Updated Feb 14, 2026

Search Tags:#development #api #codebase #validation #verification #specs

Ready to run

npx skills add https://github.com/davidabeyer/formaltask --skill validating-specs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validating-specs
Source: https://github.com/davidabeyer/formaltask/tree/main/skills/validating-specs
Command: npx skills add https://github.com/davidabeyer/formaltask --skill validating-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the costly mistake of building features based on inaccurate or non-existent code elements, ensuring that specifications align with the actual codebase before development proceeds.

Core Features & Use Cases

File Path Verification: Confirms that all file paths referenced in specifications exist within the project.
Symbol Validation: Checks for the presence and correct location of functions, classes, and other code symbols.
Library Claim Verification: Assesses the accuracy of claims made about third-party library features and versions.
Use Case: Before implementing a new API endpoint, this Skill verifies that the specified controller file, handler function, and data models actually exist and are correctly defined in the codebase.

Quick Start

Validate all spec claims against the current codebase for the 'user-authentication' epic.

Frequently Asked Questions about validating-specs

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

FAQPage Schema

What is specification validation in software development?▼

Specification validation prevents costly mistakes by confirming that file paths, functions, and classes referenced in specifications actually exist in the codebase before development proceeds. This ensures implementation targets accurate code elements.

What is the best way to prevent implementing features based on non-existent code?▼

The best way to prevent implementing non-existent code is to validate all spec claims against the current codebase before development, confirming controller files, handler functions, and data models are correctly defined.

What should I validate before implementing a new API endpoint from a specification?▼

Before implementing a new API endpoint, validate that the specified controller file, handler function, and data models actually exist and are correctly defined in the codebase to ensure accurate implementation.

When should I avoid using codebase spec validation?▼

You should avoid using codebase spec validation when specifications do not reference specific code elements, file paths, or library features, as the validation process requires concrete claims to cross-reference against the codebase.