spec-write-spec

Name: spec-write-spec
Availability: InStock
Author: GDSDN

Generate executable markdown specifications from requirements, complexity, and research inputs.

3|Updated Feb 7, 2026

Search Tags:#automation #documentation #software development #specification #requirements #traceability

Ready to run

npx skills add https://github.com/GDSDN/kord-aios --skill spec-write-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-write-spec
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/analysis/spec-write-spec
Command: npx skills add https://github.com/GDSDN/kord-aios --skill spec-write-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, executable specifications from various input artifacts, ensuring that implementation strictly follows defined requirements and research.

Core Features & Use Cases

Automated Spec Generation: Produces a spec.md file based on requirements.json, complexity.json, and research.json.
Traceability Enforcement: Ensures all spec content is directly derived from provided inputs, preventing "invention."
Use Case: After defining user stories and conducting technical research, use this Skill to generate the definitive specification document that developers will use for implementation, complete with requirements, architecture, dependencies, and test cases.

Quick Start

Use the spec-write-spec skill to generate a specification for story ID STORY-123.

Frequently Asked Questions about spec-write-spec

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

FAQPage Schema

How do I generate executable specifications from structured requirements?▼

You can generate executable specifications by feeding structured inputs like requirements, complexity analysis, and research findings into an automated generator to produce a comprehensive markdown document. This process ensures strict traceability and prevents content invention.

How does automated traceability enforcement work for software specification documents?▼

Automated traceability enforcement works by tracing all generated specification content directly back to source artifacts. This strict "no invention" policy ensures that every requirement and architectural detail is derived from provided inputs rather than generated artificially.

What input formats are needed to create an executable specification document?▼

To create an executable specification document, you need structured input files such as requirements.json, complexity.json, and research.json. These inputs provide the foundational requirements and technical research needed to generate the final spec.md file.

Can I validate specification completeness and traceability automatically?▼

Yes, you can validate specification completeness and traceability automatically. The specification generation process supports automated validation and quality gates to ensure the final document is comprehensive and fully traced to source artifacts.

What is the best way to prevent invention when generating technical specifications?▼

The best way to prevent invention when generating technical specifications is to use a generation process that enforces a strict "no invention" policy. This is achieved by tracing all content back to original source artifacts and structured inputs.

When do I need an executable specification document for software development?▼

You need an executable specification document when transitioning from user stories and technical research to implementation. It serves as the definitive guide for developers, detailing requirements, architecture, dependencies, and test cases to ensure strict adherence to defined parameters.