spec-generation

Create and validate docs/specs/<slug>/ directories with standard spec.md frontmatter.

3|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/deandum/claude-resources --skill spec-generation-deandum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-generation
Source: https://github.com/deandum/claude-resources/tree/main/skills/core/spec-generation
Command: npx skills add https://github.com/deandum/claude-resources --skill spec-generation-deandum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a formal contract for creating and validating docs/specs/<slug>/ directories, including the spec.md frontmatter and the required artifact layout, to ensure consistency across authoring, review, and session resumption.

Core Features & Use Cases

  • Enforces a fixed spec template and frontmatter schema (task, status, current_group, total_groups, created, updated) for every spec.
  • Guides the orchestration workflow by pairing with core/orchestration to populate required artifacts and manage group subtasks.
  • Supports validation, resumption, and contract-driven evolution of specs across sessions and reviews.

Quick Start

Create a new docs/specs/<slug>/ directory and begin by drafting spec.md using the provided template.

Frequently Asked Questions about spec-generation

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

FAQPage Schema
How do I enforce a standard frontmatter schema for spec documents?▼

To enforce standard spec frontmatter, define a fixed schema including task, status, current_group, total_groups, created, and updated fields to validate spec.md files. This ensures consistency across authoring, review, and session resumption.

What is the required directory structure for managing docs and specs?▼

The required structure involves creating a dedicated docs/specs/<slug>/ directory for each specification. This directory contains the spec.md file and a fixed artifact layout, supporting contract-driven evolution across sessions.

Can I resume a spec review workflow from a prior session?▼

Yes, you can resume a spec review workflow from a prior session by validating the existing frontmatter and artifact layout against the canonical template. This supports resuming group subtasks and conditional contracts.md workflows.

How do I orchestrate spec generation with subtask grouping?▼

To orchestrate spec generation with subtask grouping, pair the spec template with a core orchestration workflow to populate required artifacts and manage group subtasks. Use the current_group and total_groups frontmatter fields to track progress.

What's the best way to validate a spec template against a canonical contract?▼

The best way to validate a spec template against a canonical contract is to run a review-based check on the docs/specs/<slug>/ directory. This validates the spec.md frontmatter schema and ensures the fixed artifact layout is correctly applied.