Writing Specifications FAQs

Question 1

What does the Writing Specifications skill do?

Accepted Answer

This skill generates lean, requirement-focused feature specifications. It uses a standardized structure to define the 'what' and 'why' of a feature, prioritizing architectural standards and external documentation over implementation details to prevent bloat.

Question 2

How does this skill differ from an implementation plan?

Accepted Answer

The Writing Specifications skill focuses strictly on requirements and architecture (WHAT to build). Implementation plans, typically handled by the /plan command, break those requirements down into specific tasks and code-level dependencies (HOW to build it).

Question 3

When should I use this skill in my workflow?

Accepted Answer

Use this skill after an initial brainstorming phase but before you begin coding. It is ideal for creating a formal 'spec.md' file that defines the problem statement, functional requirements, and file-level architecture for a new feature.

Question 4

What are the 'Iron Laws' of this skill?

Accepted Answer

The Iron Laws prevent documentation rot: 1) Reference project constitutions instead of duplicating rules, 2) Link to external docs instead of embedding code examples, 3) Avoid implementation task lists, and 4) Exclude success metrics to keep the document focused on technical requirements.

Question 5

How does this skill improve development efficiency?

Accepted Answer

By creating a clear separation between requirements and implementation, it ensures architectural consistency through 'project constitutions' and keeps documentation maintainable. This prevents developers from getting bogged down in outdated code examples within spec files.

Writing Specifications

Writing Specifications

주요 기능

사용 사례

주요 기능

사용 사례