spec-generator

Generate templated markdown specification documents with metadata for implementation tasks.

3|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/CleanExpo/Synthex --skill spec-generator-cleanexpo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-generator
Source: https://github.com/CleanExpo/Synthex/tree/main/.claude/skills/spec-generator
Command: npx skills add https://github.com/CleanExpo/Synthex --skill spec-generator-cleanexpo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents implementation work from starting without a formal specification by detecting implementation-intent tasks, generating structured specification documents, and requiring review and approval before code changes proceed.

Core Features & Use Cases

  • Detection & Interception: Scans task descriptions for implementation signals (code changes, APIs, schema updates, integrations) and checks for an existing approved spec.
  • Templated Spec Generation: Produces project-phase or feature specs populated with metadata (id, type, title, status, author) using built-in templates and writes them to .claude/specs/.
  • Workflow Enforcement: Flags draft specs for review, allows approved specs to proceed to implementation, and supports an index of specs for traceability.
  • Use Case: A developer opens a task to add a new API endpoint; the Skill detects implementation intent, generates a feature spec from the task details, stores it under .claude/specs/, and prompts for approval before coding begins.

Quick Start

Generate a feature spec from the task description "Add stripe webhooks handler" and save the drafted file to .claude/specs/feature-stripe-webhooks-spec.md for review.

Frequently Asked Questions about spec-generator

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

FAQPage Schema
How do I generate a feature specification before writing code?

To generate a feature specification, provide a task description like adding an API endpoint. The Skill detects implementation intent and produces a templated markdown spec populated with metadata, saving it to .claude/specs/ for review before coding begins.

What is spec-first development and how does it enforce workflow?

Spec-first development requires a formal specification before any implementation. This enforcement mechanism intercepts tasks involving code changes or schema updates, generates structured markdown specs, and requires review approval before developers can proceed with coding.

Can I use this specification generator for third-party service integrations?

Yes, you can use this specification generator for third-party service integrations. It scans task descriptions for implementation signals including API integrations and data model modifications, then drafts a project-phase or feature spec requiring prior approval.

Does the generated specification document include project metadata?

Yes, the generated specification document includes project metadata. Each templated markdown file is populated with an id, type, title, status, and author, ensuring traceability and supporting an index of specs for project management.

What's the best way to manage draft specifications awaiting approval?

The best way to manage draft specifications is to store them in the .claude/specs/ directory. The Skill flags drafted markdown files for review, blocking implementation until the spec status is updated to approved.