spec

Maintain a single specification contract with versioning and task linkage.

69|7|Updated Jan 19, 2026

Search Tags:#versioning #documentation #specification #requirements #governance #contract #import

Ready to run

npx skills add https://github.com/TaylorHuston/local-life-manager --skill spec-taylorhuston

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill spec-taylorhuston

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams maintain a single source of truth for system specifications, ensuring alignment between requirements and implementation.

Core Features & Use Cases

External specs import and protocol spec creation for codebases and projects, including both standards and self-authored contracts.
Spec versioning, documentation structure, and task linkage to spec sections to govern development.
Use Case: When coordinating multi-project software, teams can import a standard spec and track implementation status through linked TASKs.

Quick Start

Initialize a protocol spec with /spec --init, or import an external spec with /spec --import <URL>, then create TASKs that implement specific sections and reference them.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I maintain a single source of truth for system specifications across multiple projects?▼

System specification governance maintains a single contract defining requirements. It imports external standards or self-authored protocols, enforcing frontmatter versioning and a docs structure to align implementation with requirements.

How do I link development tasks to specific specification sections?▼

You link development tasks to specific specification sections by creating TASKs that reference individual spec sections. This enforces task linkage to guide implementation and tracks completion status against the governed requirements.

What is the best way to import external standards into a codebase for requirements governance?▼

The best way to import external standards is using the import workflow. It fetches the external protocol and integrates it into the project, applying frontmatter versioning and establishing the docs structure required for governance.

How does frontmatter versioning work for protocol specs?▼

Frontmatter versioning for protocol specs enforces version tracking directly within the specification files. It maintains a single source of truth by embedding version metadata, ensuring teams sync the correct requirements across projects.

Do I need a specific docs structure to govern software specifications?▼

Yes, you need a docs structure under docs/ to govern software specifications. This enforced structure organizes the single contract and protocol files, ensuring requirements are systematically linked and tracked during development.

When do I need a specification contract for my software project?▼

You need a specification contract when coordinating multi-project software or aligning requirements with implementation. It is essential for tracking implementation status through linked TASKs and maintaining a single source of truth.