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

学習とドキュメンテーション

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.

主な機能

Generates testable functional requirements using standardized Given-When-Then syntax
Enforces a strict focus on WHAT and WHY to prevent implementation clutter
0 GitHub stars
Prevents scope creep by enforcing a 6-8 requirement limit per MVP specification
Maintains a clean directory structure separating specifications from technical details
Identifies and documents edge cases and error handling scenarios

ユースケース

Documenting product design rationale and trade-offs for stakeholders
Defining core requirements for a new feature before development begins
Creating clear acceptance criteria for QA and testing alignment

概要

主な機能

Generates testable functional requirements using standardized Given-When-Then syntax
Enforces a strict focus on WHAT and WHY to prevent implementation clutter
0 GitHub stars
Prevents scope creep by enforcing a 6-8 requirement limit per MVP specification
Maintains a clean directory structure separating specifications from technical details
Identifies and documents edge cases and error handling scenarios

ユースケース

Documenting product design rationale and trade-offs for stakeholders
Defining core requirements for a new feature before development begins
Creating clear acceptance criteria for QA and testing alignment