speckit-specify

Generate feature specifications with user stories, requirements, and acceptance criteria.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/magdymohamed78/Wasla --skill speckit-specify-magdymohamed78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/magdymohamed78/Wasla/tree/main/.agent/skills/speckit-specify
Command: npx skills add https://github.com/magdymohamed78/Wasla --skill speckit-specify-magdymohamed78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed feature specifications from high-level natural language descriptions, streamlining the initial stages of product development.

Core Features & Use Cases

  • Automated Spec Generation: Creates user stories, functional requirements, and acceptance criteria.
  • Branch Creation: Automatically generates a Git branch name based on the feature description.
  • Spec Quality Validation: Includes a checklist to ensure the generated specification meets quality standards.
  • Use Case: When a product manager describes a new feature like "Implement user profile editing with avatar upload," this Skill generates a spec.md file, a Git branch, and a quality checklist, ready for the development team.

Quick Start

Use the speckit-specify skill to create a feature specification for adding user authentication.

Frequently Asked Questions about speckit-specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate feature specifications from natural language descriptions?

Feature specifications are generated from natural language descriptions by automatically creating user stories, functional requirements, and acceptance criteria, producing a structured spec.md file ready for development planning.

Can I automate Git branch creation when starting a new feature?

Yes, Git branch creation is automated by generating a contextually appropriate branch name directly from the provided feature description, streamlining the kickoff of spec-driven development workflows.

How do I ensure my generated specification meets quality standards?

Specification quality standards are validated using an integrated checklist that verifies the completeness and clarity of user stories and acceptance criteria before the development team begins implementation.

What is the best way to write user stories and acceptance criteria from a product idea?

Writing user stories and acceptance criteria from a product idea is best handled by automating spec generation, which translates high-level natural language into comprehensive functional requirements and a validation checklist.

Does spec-driven development work without manual requirements gathering?

Spec-driven development works without manual requirements gathering by using natural language inputs to automatically generate detailed functional requirements and acceptance criteria, ensuring clarity before planning begins.