specify

name	specify
description	Create a product specification that defines what to build and why, without prescribing how.

Specify Skill

Define features with clear product specifications.

When to Activate

This skill is relevant when:

• Creating product specifications for new features
• Defining what to build and why
• Documenting user needs and acceptance criteria
• Establishing clear scope boundaries

Core Principles

Focus on Value

• Why are we building this?
• What is the user benefit?
• Clear problem statement
• Measurable success metrics

Clear Scope

• Define what is in scope
• Define what is out of scope
• Prevent scope creep
• MVP vs full feature clarity

User-Centric

• Write user stories focused on goals
• Not system functions
• Target user pain points
• Desired outcomes over implementation

Outcome-Oriented

• Describe desired outcomes
• Avoid implementation details
• No technical prescriptions
• Product thinking, not technical thinking

Quick Checks

When creating specifications, verify:

• Clear problem statement exists
• Goals are well-defined and measurable
• User stories follow "As a [role], I want to [action] so that [benefit]"
• Acceptance criteria are specific and testable
• Functional requirements defined
• UI/UX expectations documented
• Performance expectations set
• Edge cases identified (empty states, errors, boundaries)
• Out of scope explicitly stated
• Success metrics defined
• No technical implementation details included
• No API endpoint designs
• No database schemas
• No architecture decisions
• No code structure or patterns