draft-spec

Generate technical reference documentation verified against source code.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill draft-spec-covcloud-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-spec
Source: https://github.com/Covcloud-LLC/adhd-workflow/tree/main/skills/draft-spec
Command: npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill draft-spec-covcloud-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of documentation rot and ambiguity by ensuring that technical specifications are always grounded in the current state of the codebase and verified against actual source artifacts.

Core Features & Use Cases

  • Grep-Verified Documentation: Automatically validates field names, types, and examples against the actual emitting or consuming source code.
  • Machine-Scannable Output: Produces fact-dense tables and schemas optimized for both human developers and automated context-collecting bots.
  • Use Case: When building a new API endpoint, use this skill to generate a reference document that is guaranteed to match the implementation, preventing the common issue of documentation drifting from the actual code.

Quick Start

Use the draft-spec skill to document the user-profile-api schema by verifying it against the current repository source code.

Frequently Asked Questions about draft-spec

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

FAQPage Schema
Do I need source code fixtures in my repository to verify technical specifications?

To generate verified API documentation, cross-reference technical specifications against authoritative source code, endpoints, or fixtures within the repository to prevent documentation rot. This ensures field names, types, and examples match the actual implementation.

Do I need source code fixtures in my repository to verify technical specifications?

Prevent documentation drift by generating reference documents that are strictly verified against the current codebase. This guarantees the technical specifications match the actual implementation, eliminating ambiguity and keeping outputs fact-dense.

Do I need source code fixtures in my repository to verify technical specifications?

Grep-verified documentation works by automatically validating field names, types, and examples against the actual emitting or consuming source code within your repository. This ensures all schema documentation is fact-dense and grounded in the current codebase state.

Do I need source code fixtures in my repository to verify technical specifications?

Yes, you can generate machine-scannable reference documents for configuration surfaces by producing fact-dense tables and schemas. These outputs are optimized for both human developers and automated context-collecting bots to easily parse.

Do I need source code fixtures in my repository to verify technical specifications?

Yes, you need authoritative source code, endpoints, or fixtures within your repository to verify technical specifications. The documentation process requires strict adherence to fact-dense formatting and automated verification of all field names and types against these artifacts.