spec-guide

Generate Executable Implementation Specs from natural language descriptions.

Updated Apr 20, 2026

Search Tags:#developer tools #specification #project documentation #EIS #codebase grounding

Ready to run

npx skills add https://github.com/esxr/product-wiki --skill spec-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-guide
Source: https://github.com/esxr/product-wiki/tree/main/skills/eis-writing
Command: npx skills add https://github.com/esxr/product-wiki --skill spec-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of creating detailed and precise Executable Implementation Specs (EIS) from natural language descriptions, ensuring compliance with coding standards and project requirements.

Core Features & Use Cases

Natural Language Input: Generate EIS from a description, saving time and reducing manual errors.
Format Guidance: Ensures the EIS follows the established format with required sections and naming conventions.
Grounding Rule Compliance: Requires verification against the codebase before writing, ensuring accuracy.
Wiki Companion: Automatically creates a summary in the project's wiki for documentation and reference.

Quick Start

Create a new EIS by using the command: /create-feature "A new feature to add a payment gateway."

Frequently Asked Questions about spec-guide

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

FAQPage Schema

How do I generate executable implementation specs from natural language descriptions?▼

You can generate executable implementation specs by inputting a natural language feature description, which the system automatically translates into structured markdown with predefined sections and format guidelines.

What is an executable implementation spec and when do I need one for project documentation?▼

An executable implementation spec is a structured markdown document that defines precise feature requirements aligned with codebase specifics, needed when translating natural language features into actionable development guidelines.

Do I need codebase access to create project documentation with this approach?▼

Yes, codebase access is required to verify grounding rules, ensuring the generated project documentation and specifications accurately align with existing project requirements and codebase specifics.

How to maintain and update an existing executable implementation spec?▼

You maintain an executable implementation spec by updating the natural language description and regenerating the structured markdown, which automatically syncs the project wiki summary and verifies codebase alignment.

What's the best way to ensure specification format compliance with predefined sections?▼

The best way to ensure specification format compliance is to use automated generation tools that enforce predefined sections, required naming conventions, and structured data outputs based on your feature description.

Can I automatically create a wiki summary when generating project specifications?▼

Yes, the system automatically creates a summary in the project's wiki for documentation and reference whenever a new project specification is generated from your natural language input.