spec-creator

Generate implementation-grade SPEC.md documents through a four-phase workflow.

1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/praxstack/skills-and-personas --skill spec-creator-praxstack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-creator
Source: https://github.com/praxstack/skills-and-personas/tree/main/skills/spec-creator
Command: npx skills add https://github.com/praxstack/skills-and-personas --skill spec-creator-praxstack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

spec-creation eliminates the guesswork between high-level ideas and concrete code by producing portable, implementation-grade SPEC.md documents that can be used by AI coding agents to implement systems without back-and-forth questions.

Core Features & Use Cases

  • Phase-driven workflow: intake/calibration, brainstorming rounds, drafting, and self-review to produce a complete SPEC.md.
  • Self-contained contracts: outputs a single Markdown file that agents can implement against with zero follow-up questions.
  • Extensible guidance: references, quality rubrics, templates, and self-review checks to ensure production-grade quality.
  • Suitable for backend services, CLIs, SDKs, and full-stack tools requiring explicit implementation contracts.

Quick Start

Observe a user input describing a software task and generate a portable SPEC.md that fully defines the system, its constraints, and how to implement it.

Frequently Asked Questions about spec-creator

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

FAQPage Schema
How do I create implementation specifications for AI coding agents?

Implementation specifications for AI coding agents are created by generating a portable SPEC.md file. This document acts as a complete contract between architecture and code, enabling automated implementation without follow-up questions.

What is the best way to write portable software specifications before coding?

The best way to write portable software specifications is using a four-phase workflow: intake, brainstorming, drafting, and self-review. This process outputs a self-contained SPEC.md document that defines system constraints and implementation details.

Can I use a single specification file for backend services and full-stack tools?

Yes, a single SPEC.md specification file can be used for backend services, CLIs, SDKs, and full-stack tools. It serves as an explicit implementation contract suitable for any software task requiring thorough specifications.

How does a phase-driven workflow improve software specification drafting?

A phase-driven workflow improves software specification drafting by enforcing intake calibration, brainstorming rounds, drafting, and self-review. This structured approach ensures the final SPEC.md meets production-grade quality rubrics and template standards.

Do I need to provide architectural constraints to generate a software contract?

Yes, you need to provide architectural constraints during the intake phase to generate a software contract. The resulting SPEC.md fully defines the system boundaries and requirements to guide subsequent code implementation.