/speckit.specify

description: Create or update the feature specification from a natural language feature description.

User Input

$ARGUMENTS

You **MUST** consider the user input before proceeding (if not empty).

Outline

The text the user typed after `/speckit.specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `$ARGUMENTS` appears literally below. Do not ask the user to repeat it unless they provided an empty command.

Given that feature description, do this:

1. **Generate a concise short name** (2-4 words) for the branch:

• Analyze the feature description and extract the most meaningful keywords
• Create a 2-4 word short name that captures the essence of the feature
• Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
• Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
• Keep it concise but descriptive enough to understand the feature at a glance
• Examples:
• "I want to add user authentication" → "user-auth"
• "Implement OAuth2 integration for the API" → "oauth2-api-integration"
• "Create a dashboard for analytics" → "analytics-dashboard"
• "Fix payment processing timeout bug" → "fix-payment-timeout"

2. Run the script `.specify/scripts/powershell/create-new-feature.ps1 -Json "$ARGUMENTS"` from repo root **with the short-name argument** and parse its JSON output for BRANCH_NAME and SPEC_FILE. All file paths must be absolute.

**IMPORTANT**:

• Append the short-name argument to the `.specify/scripts/powershell/create-new-feature.ps1 -Json "$ARGUMENTS"` command with the 2-4 word short name you created in step 1
• Bash: `--short-name "your-generated-short-name"`
• PowerShell: `-ShortName "your-generated-short-name"`
• For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot")
• You must only ever run this script once
• The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for

3. Load `.specify/templates/spec-template.md` to understand required sections.

4. Follow this execution flow:

1. Parse user description from Input If empty: ERROR "No feature description provided" 2. Extract key concepts from description Identify: actors, actions, data, constraints 3. For unclear aspects:

• Make informed guesses based on context and industry standards
• Only mark with [NEEDS CLARIFICATION: specific question] if:
• The choice significantly impacts feature scope or user experience
• Multiple reasonable interpretations exist with different implications
• No reasonable default exists
• **LIMIT: Maximum 3 [NEEDS CLARIFICATION] markers total**
• Prioritize clarifications by impact: scope > security/privacy > user experience > technical details

4. Fill User Scenarios & Testing section If no clear user flow: ERROR "Cannot determine user scenarios" 5. Generate Functional Requirements Each requirement must be testable Use reasonable defaults for unspecified details (document assumptions in Assumptions section) 6. Define Success Criteria Create measurable, technology-agnostic outcomes Include both quantitative metrics (time, performance, volume) and qualitative measures (user satisfaction, task completion) Each criterion must be verifiable without implementation details 7. Identify Key Entities (if data involved) 8. Return: SUCCESS (spec ready for planning)

5. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.

6. **Specification Quality Validation**: After writing the initial spec, validate it against quality criteria:

a. **Create Spec Quality Checklist**: Generate a checklist file at `FEATURE_DIR/checklists/requirements.md` using the checklist template structure with these validation items:

      # Specification Quality Checklist: [FEATURE NAME]
      
      **Purpose**: Validate specification completeness and quality before proceeding to planning
      **Created**: [DATE]
      **Feature**: [Link to spec.md]
      
      ## Content Quality
      
      - [ ] No implementation details (languages, frameworks, APIs)
      - [ ] Focused on user value and business needs
      - [ ] Written for non-technical stakeholders
      - [ ] All mandatory sections completed
      
      ## Requirement Completeness
      
      - [ ] No [NEEDS CLARIFICATION] markers remain
      - [ ] Requirements are testable and unambiguous
      - [ ] Success criteria are measurable
      - [ ] Success criteria are technology-agnostic (no implementation details)
      - [ ] All acceptance scenarios are defined
      - [ ] Edge cases are identified
      - [ ] Scope is clearly bounded
      - [ ] Dependencies and assumptions identified
      
      ## Feature Readiness
      
      - [ ] All functional requirements have clear acceptance criteria
      - [ ] User scenarios cover primary flows
      - [ ] Feature meets measurable outcomes defined in Success Criteria
      - [ ] No implementation details leak into specification
      
      ## Notes
      
      - Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`

b. **Run Validation Check**: Review the spec against each checklist item:

• For each item, determine if it passes or fails
• Document specific issues found (quote relevant spec sections)

c. **Handle Validation Results**:

• **If all items pass**: Mark checklist complete and proceed to step 6

• **If items fail (excluding [NEEDS CLARIFICATION])**:

1. List the failing items and specific issues