write-spec

Generates structured technical specifications with acceptance criteria and decision rationales from vague feature ideas.

23|2|Updated Mar 7, 2026

Search Tags:#automation #architecture #documentation #specification #review #write-spec

Ready to run

npx skills add https://github.com/kirich1409/krozov-ai-tools --skill write-spec-kirich1409

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/developer-workflow/skills/write-spec
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill write-spec-kirich1409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specification-driven development transforms vague feature requests into a precise, actionable spec, including research, interviews, and structured documentation that serves as a contract for autonomous implementation.

Core Features & Use Cases

Generates a comprehensive spec with acceptance criteria, affected modules, constraints, and decisions.
Autoreviews the spec via self-review and multiexpert-review, then saves the document as a permanent artifact.
Supports proactive scoping and planning for complex features before any code is written.

Quick Start

Describe a feature idea and let the skill generate a complete spec draft ready for review.

Frequently Asked Questions about write-spec

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

FAQPage Schema

How do I automate technical specification creation from a vague feature idea?▼

Automating technical specification creation transforms vague ideas into precise docs by generating acceptance criteria, affected modules, and technical approaches. The skill drafts a comprehensive specification and performs automated reviews before saving the final artifact.

What is specification-driven development and when do I need it for complex features?▼

Specification-driven development formalizes multi-step features into structured documentation before implementation. You need it for cross-team collaboration and architecture thinking where a formal contract with technical constraints and rationales is required.

How do I generate acceptance criteria and technical constraints before writing any code?▼

Generating acceptance criteria and technical constraints requires researching the feature scope and conducting interviews. The skill produces a structured spec containing these sections, along with affected modules and decisions made, ready for multiexpert review.

Can I use automated self-review and multiexpert review for architecture documentation?▼

Yes, automated self-review and multiexpert review validate architecture documentation by evaluating the generated technical approach and constraints. The skill runs these review processes automatically on the spec draft to ensure completeness before finalizing the artifact.

What is the best way to document cross-team collaboration requirements for software engineering?▼

The best way to document cross-team collaboration is creating a structured specification that outlines technical constraints and decisions. This skill automates that process, generating a permanent artifact that serves as an actionable contract for autonomous implementation.