speckit-specify
Originally fromdceoy/speckit-agent-skills
Installation
SKILL.md
Speckit Specify Skill
Outline
The user's message that triggered this skill is the feature description. Do not ask the user to repeat it unless they provided no description.
Given that feature description, do this:
- 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"
Related skills
More from h3y6e/speckit-skills
speckit-clarify
Structured clarification workflow for underspecified requirements. Use
15speckit-analyze
Perform cross-artifact consistency analysis across spec.md, plan.md,
15speckit-plan
Generate technical implementation plans from feature specifications.
15speckit-tasks
Break down implementation plans into actionable task lists. Use after
14speckit-implement
Execute all tasks from the task breakdown to build the feature. Use after
12speckit-constitution
Create or update project governing principles and development guidelines.
12