write-spec

Creates feature specifications from plain-language descriptions following GitHub Spec Kit structure.

22|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/handarbeit/fabrik --skill write-spec-handarbeit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/handarbeit/fabrik/tree/main/plugin/entwurf/skills/write-spec
Command: npx skills add https://github.com/handarbeit/fabrik --skill write-spec-handarbeit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a rough feature idea into a specification a development team can build from is hard for product managers and business owners who don't write software. This Skill converts a plain-language feature description into a structured, quality-checked feature specification without requiring any technical knowledge. ## Core Features & Use Cases - Structured Spec Generation: Writes a numbered specs/NNN-short-name/spec.md following GitHub Spec Kit's template, with prioritized user stories, edge cases, functional requirements, and measurable success criteria. - Quality Validation: Generates a 16-item requirements checklist, scores the spec against it, and repairs failures before delivery. - Guided Clarification: Asks up to three high-impact clarifying questions with recommendations, and records answers and assumptions separately so business decisions stay distinguishable from guesses. - Use Case: A restaurant operations manager describes wanting to track food waste across sites; the Skill produces a complete, non-technical spec with prioritized user stories and measurable outcomes, ready to hand to engineers. ## Quick Start Ask the assistant to spec out a feature by describing it in plain language, for example: write a spec for a feature that lets staff record food waste at the end of each shift.

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 feature specification without technical knowledge?

Describe the feature in plain language and the Skill generates a complete spec with prioritized user stories, functional requirements, and success criteria. It asks at most three clarifying questions, each with a recommendation, and never requires engineering knowledge to answer.

What is GitHub Spec Kit's specify workflow?

It is a specification structure where each feature gets a numbered folder under specs/ containing a spec.md and a requirements quality checklist, plus a .specify/feature.json pointer to the active feature. The spec covers what users need and why, never how to implement it.

Can I update an existing spec instead of creating a new one?

Yes. The Skill detects revision requests like adding a user story or changing a priority, edits the existing spec in place, and re-runs the quality checklist. It never allocates a new feature number for a change to an existing spec.

What happens when a success criterion has no measurable number?

The Skill writes the measurable shape of the criterion and marks the missing figure as [NEEDS BASELINE] rather than inventing a number. It may ask what the business currently tracks, and records unresolved baselines in the final report.

Does the spec include technical implementation details?

No. The spec deliberately excludes languages, frameworks, databases, and APIs. When a description mentions a technology, the Skill captures the underlying business need in the spec and notes the stated preference under Assumptions.