write-spec

Name: write-spec
Availability: InStock
Author: sambeau

Generate structured specifications with requirements, acceptance criteria, and verification plans from approved designs.

5|Updated Mar 18, 2026

Search Tags:#design #specification #requirements #verification #review #traceability #cross-reference

Ready to run

npx skills add https://github.com/sambeau/kanbanzai --skill write-spec-sambeau

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/sambeau/kanbanzai/tree/main/.kbz/skills/write-spec
Command: npx skills add https://github.com/sambeau/kanbanzai --skill write-spec-sambeau

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Converts approved design documents into formal, review-ready specifications that define scope, traceability, acceptance criteria, and verification plans to prevent misinterpretation and scope creep.

Core Features & Use Cases

Template-driven specification authoring with structured sections (Problem Statement, Requirements, Constraints, Acceptance Criteria, Verification Plan)
Cross-reference to the parent design document to ensure alignment and traceability
Enforced testability: each requirement maps to verifiable acceptance criteria and a verification plan
Scope management: explicit in-scope and out-of-scope statements to guide reviews and implementations

Quick Start

Submit an approved design document and invoke the spec writer to generate a draft specification.

Frequently Asked Questions about write-spec

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

FAQPage Schema

How do I write a gate-checkable specification from an approved design?▼

To write a gate-checkable specification, submit an approved design document to generate a structured specification. The output includes a problem statement, functional and non-functional requirements, constraints, acceptance criteria, and a verification plan.

What is the best way to ensure requirements traceability to acceptance criteria?▼

Ensuring requirements traceability requires mapping each functional and non-functional requirement directly to verifiable acceptance criteria. This cross-reference to the parent design document prevents scope creep and enables independent review.

How do I generate a verification plan for product requirements?▼

Generating a verification plan involves structuring testable requirements alongside explicit in-scope and out-of-scope statements. This ensures every requirement is covered by a verification plan to enable independent review.

Can I use a template to create a formal specification with functional and non-functional requirements?▼

Yes, template-driven specification authoring generates a formal specification with structured sections. It produces a complete specification covering problem statements, constraints, acceptance criteria, and a verification plan from an approved design.

How to prevent scope creep when converting design documents into formal specifications?▼

Preventing scope creep requires explicit in-scope and out-of-scope statements within the formal specification. Cross-referencing the parent design document ensures alignment and traceability to guide reviews and implementations.