speckit-specify

# Speckit Specify Skill ## User Input ```text $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. **Check for existing branches before creating new one**: a. First, fetch all remote branches to ensure we have the latest information: ```bash git fetch --all --prune ``` b. Find the highest feature number across all sources for the short-name: - Remote ...