Where are the generated specifications stored?

Specifications are organized in a dedicated 'specs' directory, with each feature getting its own date-stamped folder containing a README.md for requirements and a technical-details.md for implementation.

Does this skill include code examples or architecture diagrams?

No, this skill specifically excludes implementation details like code, database schemas, or API signatures to focus entirely on the functional requirements and business value.

How does the skill handle large features that exceed the requirement limit?

If a feature requires more than 6-8 requirements, the skill flags it as too large and helps you identify core requirements for the MVP while moving the rest to a separate specification.

What is the Given-When-Then format used for?

It is a structured way to write acceptance criteria that ensures every requirement is testable by defining the context (Given), the action (When), and the expected result (Then).

Spec Writing Professional

Name: Spec Writing Professional
Author: jkappers

byjkappers

0•

Learning & Documentation

Generates structured feature specifications focusing on requirements and acceptance criteria to define project scope and goals.

The Spec Writing Professional skill streamlines the software delivery process by guiding Claude to create comprehensive feature specifications that define the 'what' and 'why' of a project. By enforcing a standardized structure—including success criteria, design rationale, and functional requirements using the Given-When-Then format—it ensures that development teams have clear, testable, and MVP-focused documentation. This skill helps prevent scope creep and technical debt by separating high-level requirements from low-level implementation details, facilitating better alignment between product, design, and engineering teams.

Key Features

01Generates testable functional requirements using standardized Given-When-Then syntax

02Enforces a strict focus on WHAT and WHY to prevent implementation clutter

030 GitHub stars

04Prevents scope creep by enforcing a 6-8 requirement limit per MVP specification

05Maintains a clean directory structure separating specifications from technical details

06Identifies and documents edge cases and error handling scenarios

Use Cases

01Documenting product design rationale and trade-offs for stakeholders

02Defining core requirements for a new feature before development begins

03Creating clear acceptance criteria for QA and testing alignment

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jkappers/claude-code-software-delivery-plugin writing-specs

For use in Claude.ai and ChatGPT

Download Skill