spec-writer-minimal

Convert rough briefs into structured feature specifications with fixed sections.

Updated Mar 17, 2026

Search Tags:#planning #documentation #specification #requirements #clarification #product-management

Ready to run

npx skills add https://github.com/saboteur-labs/ai-workflows --skill spec-writer-minimal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-writer-minimal
Source: https://github.com/saboteur-labs/ai-workflows/tree/main/skills/planning/spec-writer-minimal
Command: npx skills add https://github.com/saboteur-labs/ai-workflows --skill spec-writer-minimal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing precise, testable feature specs from vague briefs to reduce ambiguity and rework.

Core Features & Use Cases

Converts rough briefs into a structured spec with Overview, Goals, Non-goals, Functional requirements, and Open questions.
Enforces a concise length and a no-implementation policy to focus on what, not how.
Supports clarifying questions before drafting when briefs are ambiguous.

Quick Start

Provide a complete spec from a brief, e.g., "Add user profiles with social login", and return a finished spec document.

Frequently Asked Questions about spec-writer-minimal

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

FAQPage Schema

How do I write a feature specification from a rough product brief?▼

To write a feature specification from a rough brief, convert the brief into a structured document covering Overview, Goals, Non-goals, Functional requirements, and Open questions, strictly focusing on what the feature does without implementation details.

What is the best way to structure early concept validation for product features?▼

Early concept validation for product features is best structured by drafting a concise specification under 400 words that defines Goals and Non-goals, lists functional requirements, and highlights open questions to clarify ambiguity before development.

Can I use this approach to create requirements for ambiguous product briefs?▼

Yes, you can create requirements for ambiguous briefs by triggering a clarification phase that identifies missing context, then drafting a precise specification document that enforces a strict structure and a concise length to reduce rework.

How do I keep feature specs concise without losing key product requirements?▼

To keep feature specs concise without losing requirements, enforce a fixed structure with an under-400-word limit and a no-implementation policy. This forces the specification to focus only on functional outcomes and testable goals.

Why does my feature specification include too many implementation details?▼

Feature specifications include too many implementation details when they lack a strict no-implementation policy. You must enforce a fixed structure that separates functional requirements from technical execution to focus entirely on what the product needs to do.

Does spec-writer-minimal support drafting testable feature specs from vague briefs?▼

Yes, spec-writer-minimal supports drafting testable feature specs from vague briefs by converting rough inputs into a structured format that reduces ambiguity and explicitly outlines functional requirements and open questions.