spec-writing

Name: spec-writing
Availability: InStock
Author: kaptinlin

placeholder

23|2|Updated Jun 9, 2025

Search Tags:#documentation #acceptance criteria #decision records #specs #spec-writing #project briefs

Ready to run

npx skills add https://github.com/kaptinlin/gozod --skill spec-writing-kaptinlin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-writing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/spec-writing
Command: npx skills add https://github.com/kaptinlin/gozod --skill spec-writing-kaptinlin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specification writing for non-code projects is often ad-hoc, leading to vague requirements, unclear scope, and misaligned teams. This Skill provides a structured approach to capture goals, constraints, decisions, and acceptance criteria in a single, shareable document.

Core Features & Use Cases

Unified specs for research, content, product, and marketing initiatives, ensuring a single source of truth.
Inline decision records (Why/Rejected) to document trade-offs and rationale alongside rules.
Acceptance criteria and clear scope boundaries to enable verifiable execution and future auditing.

Quick Start

Draft a unified spec following the standard domain patterns (00-50) with inline decisions and acceptance criteria.

Frequently Asked Questions about spec-writing

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

FAQPage Schema

How do I write specifications for non-code projects to ensure clear scope?▼

To write specifications for non-code projects, draft a unified document capturing goals, constraints, and acceptance criteria. This ensures clear scope and aligned teams by providing a single source of truth for research, content, product, and marketing initiatives.

What is the best way to document decision rationales and trade-offs in project briefs?▼

The best way to document decision rationales in project briefs is using inline decision records. This captures the "Why" and "Rejected" trade-offs directly alongside the rules, ensuring the rationale remains contextually linked to the specifications.

How do I structure a project spec to include acceptance criteria and success metrics?▼

Structure your project spec using the standard 00-50 domain pattern. This framework systematically integrates acceptance criteria, success metrics, and validation rules, enabling verifiable execution and future auditing of the project's outcomes.

Can I use this spec-writing approach for marketing and research initiatives?▼

Yes, you can use this spec-writing approach for marketing and research initiatives. It creates unified specs across product, content, and marketing domains, ensuring every initiative has defined boundaries and verifiable acceptance criteria.

Why do my project specifications often lead to misaligned teams and vague requirements?▼

Project specifications often lead to misaligned teams and vague requirements when written ad-hoc. Applying a structured approach with documented constraints, decision records, and acceptance criteria resolves this by establishing a single, shareable source of truth.