spec

Define consistent specification conventions for mdvs documentation and workflows.

27|2|Updated Feb 22, 2026

Search Tags:#templates #documentation #standards #spec #frontmatter #terminology #cross-reference

Ready to run

npx skills add https://github.com/edochi/mdvs --skill spec-edochi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/edochi/mdvs/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/edochi/mdvs --skill spec-edochi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a single source of truth for terms, storage formats, and command/workflow specs across mdvs projects, preventing duplication and drift.

Core Features & Use Cases

Canonical terminology and reference standards to avoid conflicting definitions
Uniform templates for command, workflow, and terminology specs to ensure consistency
Use case: when drafting new specification documents, follow these conventions to maintain alignment across teams and tools

Quick Start

Follow the Spec Document Conventions to draft and review new specification documents.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I enforce consistent specification conventions across documentation?▼

To enforce consistent specification conventions across documentation, apply standard header formats, frontmatter rules, and uniform templates for command and workflow docs to ensure structural alignment.

What are specification templates for command and workflow docs?▼

Specification templates for command and workflow docs provide predefined structures for headers, sections, and cross-reference rules, ensuring uniform style and preventing duplication across all specification documents.

How do I maintain canonical terminology and prevent definition drift across projects?▼

Maintain canonical terminology and prevent definition drift by establishing a single source of truth for terms, storage formats, and shared types, applying consistent cross-reference rules across all specification documents.

Does this spec convention tool support cross-referencing and frontmatter guidance?▼

Yes, this spec convention tool supports cross-referencing and frontmatter guidance, providing specific rules for headers, sections, and diagram tooling to maintain uniform structure across terminology and workflow specifications.

What is the best way to structure specification documents for shared types and storage formats?▼

The best way to structure specification documents for shared types and storage formats is using standardized templates that define header formats, frontmatter requirements, and section ordering to prevent conflicting definitions.

When do I need specification document conventions for my project?▼

You need specification document conventions when drafting new specification documents or managing terminology, storage formats, and workflow specs across teams, ensuring alignment and preventing documentation drift.