spec-writer

Draft structured feature specifications through guided clarifying questions.

Updated Mar 17, 2026

Search Tags:#planning #dialogue #clarification #product-management #spec-writing #feature-spec

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Drafts precise, implementable feature specifications through guided dialogue that surfaces ambiguities and constraints.

Core Features & Use Cases

Guided clarification: The skill prompts for 2-3 targeted questions to align scope before drafting.
Structured spec drafting: Produces a complete specification with sections such as Overview, Goals, Non-goals, User stories, Functional requirements, Open questions, and Out of scope.
Review-ready output: Highlights decisions and remaining uncertainties for user confirmation.

Quick Start

Provide a concise brief of a feature idea and the skill will start a guided dialogue to draft a full spec.

Frequently Asked Questions about spec-writer

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

FAQPage Schema

How do I write a feature spec from a rough product idea?▼

Feature specs require a guided dialogue that asks 2-3 targeted clarifying questions to surface ambiguities and constraints before drafting. This ensures alignment and scope clarity by producing a structured specification with explicit requirements and decision points for review.

What should be included in a feature specification for product management?▼

A feature specification should include Overview, Goals, Non-goals, User stories, Functional requirements, Open questions, and Out of scope sections. This structured format highlights explicit requirements and decision points for review-ready alignment.

Can I draft functional requirements without fully defining the project scope?▼

Drafting functional requirements without defined scope risks misalignment. The guided clarification process asks targeted questions to establish non-goals and out-of-scope items first, ensuring the final spec maintains strict scope clarity and actionable constraints.

What is the best way to identify ambiguities and constraints before writing a spec?▼

The best way to identify ambiguities and constraints before writing a spec is through a guided dialogue. Answering 2-3 targeted clarifying questions surfaces hidden uncertainties, allowing you to resolve decision points and define explicit functional requirements.

How do I handle open questions and decision points when planning a feature?▼

To handle open questions when planning a feature, consolidate them into a dedicated section of the spec. The drafting process explicitly highlights remaining uncertainties and decision points, delivering a review-ready document for stakeholder confirmation.