write-spec

Generate structured product or technical specs with diagrams and acceptance criteria.

1|Updated Apr 22, 2026

Search Tags:#architecture #documentation #requirements #review #spec #acceptance-criteria

Ready to run

npx skills add https://github.com/terencefan/inority-workspace --skill write-spec-terencefan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert vague or local context into a structured, reviewable specification that defines scope, assumptions, design, and acceptance criteria.

Core Features & Use Cases

Draft product specs that clarify user problems, goals, scope, UX, and success metrics.
Generate technical specs covering architecture, data flows, interfaces, and migration plans, with explicit acceptance criteria.
Load appropriate templates from the repository and adapt headings and language to match project conventions.
Provide a ready-to-review document with diagrams and a clear runbook-driven interview record for validation.

Quick Start

Provide rough requirements or local repo context and request a full product or technical spec.

Frequently Asked Questions about write-spec

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

FAQPage Schema

How do I turn rough requirements into a review-ready technical spec?▼

A product spec clarifies user problems, goals, scope, UX, and success metrics. Generating one from vague context involves structuring assumptions, design decisions, and runbook-driven interview records into a reviewable document.

How do I write acceptance criteria for a software architecture document?▼

Writing acceptance criteria for a software architecture document involves defining explicit validation standards for the system. The spec generation process handles this by tailoring headings and diagrams to include measurable acceptance criteria sections.

Can I generate both product and technical specs from the same local repo context?▼

Generating diagram-driven specifications from local repository context involves loading templates and adapting them to project conventions. This produces a structured, review-ready document with visual architecture overviews and module divisions.

What is the best way to structure design decisions and assumptions in a spec?▼

The best way to structure design decisions and assumptions in a spec is to separate them into dedicated sections. This approach explicitly defines scope, constraints, and design choices to create a clear, reviewable validation document.