spec-writer

Convert PLAN.md into a standardized SPEC.md with data contracts and validation rules.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill spec-writer-hoonzinope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/hoonzinope/skills/tree/main/spec-writer
Command: npx skills add https://github.com/hoonzinope/skills --skill spec-writer-hoonzinope

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Converts a planning document into a precise SPEC.md that captures inputs, outputs, data contracts, errors, and boundary conditions so engineering teams can implement with a clear contract.

Core Features & Use Cases

  • Convert a PLAN.md into a formal SPEC.md with clearly defined inputs, outputs, data models, and validation rules.
  • Document error handling, edge cases, and open questions to ensure a complete contract for developers and QA.
  • Use case: generate a SPEC.md from an existing plan to hand to engineers before implementation.

Quick Start

Generate a SPEC.md from the existing plan in .documents/plan/PLAN.md.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I convert a project plan into a specification document for engineering handoff?

To convert a project plan into a specification document, this Skill reads your PLAN.md and generates a SPEC.md that defines inputs, outputs, data models, validation rules, and edge cases for engineering teams.

What should be included in a specification to cover edge cases and data contracts?

A specification covering edge cases and data contracts must include explicit data models, validation rules, error handling, boundary conditions, and open questions to ensure developers and QA have a complete implementation contract.

How do I generate a SPEC.md from an existing planning document?

You can generate a SPEC.md from a planning document by placing your PLAN.md inside the .documents/plan directory, which the Skill processes to produce a standardized specification with versioning and open questions.

Can I define data models and validation rules from a plan automatically?

Yes, you can define data models and validation rules automatically from a plan, as the Skill extracts your planning requirements and formalizes them into concrete data contracts and boundary case definitions.

Do I need a specific file format to create requirements and specifications for QA teams?

You need a PLAN.md file located in the .documents/plan directory to create requirements and specifications for QA teams, serving as the input for generating the standardized SPEC.md output.

When should I formalize a plan into a spec versus handing the plan directly to engineers?

You should formalize a plan into a spec when engineering teams need explicit data contracts, validation rules, and boundary conditions to implement against, rather than relying on an informal planning document.