create-spec

Name: create-spec
Availability: InStock
Author: kinnerkarmanish

Generate implementation-ready specs with YAML test data across nine phases.

Updated Apr 26, 2026

Search Tags:#automation #workflow #testing #architecture #specification #requirements #yaml

Ready to run

npx skills add https://github.com/kinnerkarmanish/mak --skill create-spec-kinnerkarmanish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/kinnerkarmanish/mak/tree/main/library/skills/development/create-spec
Command: npx skills add https://github.com/kinnerkarmanish/mak --skill create-spec-kinnerkarmanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating comprehensive software specifications is often manual, fragmented, and error-prone. This skill provides an end-to-end, structured workflow that guides teams through 9 distinct phases to produce a complete, implementation-ready spec for library, feature, or change types.

Core Features & Use Cases

9-phase guided workflow (discovery, context gathering, requirements, constraints, architecture, interfaces, error handling, testing strategy, assembly) to ensure thorough coverage.
Supports three spec types (library, feature, change) with type-specific templates and outputs.
Generates YAML test data alongside the final spec to accelerate test-driven development and validation.

Quick Start

Run /create-spec --type feature to start an interactive guided spec creation.

Frequently Asked Questions about create-spec

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

FAQPage Schema

How do I automate software specification creation for feature and library types?▼

Automate software specification creation by running a guided 9-phase workflow that progresses from discovery through testing strategy. It supports library, feature, and change types with type-specific templates to ensure consistent, implementation-ready outputs.

What is the best way to generate YAML test data alongside my requirements document?▼

Generate YAML test data alongside your final specification by using an automated workflow that integrates testing strategy phases into the document creation process. This accelerates test-driven development and validation directly from the generated spec.

Can I use a structured workflow to define software architecture and error handling requirements?▼

Yes, you can define software architecture and error handling requirements using a structured 9-phase workflow. The process explicitly includes dedicated phases for architecture, interfaces, and error handling to ensure thorough specification coverage.

How do I create implementation-ready specifications in a team environment?▼

Create implementation-ready specifications in a team environment by applying an interactive or autonomous guided workflow. This enforces consistent phase-driven templates and outputs, reducing manual fragmentation and errors in collaborative software design.

Does the specification workflow support different project types like changes and new features?▼

The specification workflow supports three distinct project types: library, feature, and change. Each type utilizes specific templates and generates tailored outputs to ensure the final document accurately reflects its unique architectural and testing requirements.

What are the limitations of using a 9-phase structured workflow for software requirements?▼

A limitation of a 9-phase structured workflow is its rigid coverage scope, which requires progressing through discovery, constraints, and assembly phases sequentially. This approach may be excessive for minor updates that do not need comprehensive architectural or testing strategy documentation.