skills.rest
LISSConsulting
LISSConsultingOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-specify

Generate spec.md files with user stories, requirements, and acceptance criteria.

1|Updated Feb 23, 2026
Search Tags:#git#documentation#development workflow#specification#requirements#feature
One-click install
npx skills add https://github.com/LISSConsulting/RalphSpec --skill speckit-specify-lissconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/LISSConsulting/RalphSpec/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/LISSConsulting/RalphSpec --skill speckit-specify-lissconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation and refinement of feature specifications from natural language descriptions, ensuring a structured and comprehensive starting point for development.

Core Features & Use Cases

  • Automated Spec Generation: Creates detailed spec.md files including user stories, functional requirements, and acceptance criteria.
  • Branch Naming & Numbering: Intelligently suggests and assigns branch names and numbers based on existing project conventions.
  • Use Case: When a product manager describes a new feature like "Implement a user profile editing page with avatar upload," this Skill generates the initial spec.md and suggests a Git branch name like 1-user-profile-edit.

Quick Start

Use the speckit-specify skill to create a new feature specification for "Add dark mode toggle to the application".

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?▼

You can generate feature specifications by providing a natural language description of the feature, which produces a structured spec.md file with user stories, functional requirements, and acceptance criteria.

How does spec-driven development handle Git branch naming and numbering?▼

Spec-driven development handles Git branch naming by determining the next available feature number and short name, creating structured branches like '1-user-profile-edit' based on your project's existing conventions.

What is included in an automated feature specification file?▼

An automated feature specification file includes structured user stories, functional requirements, and acceptance criteria designed to provide a comprehensive starting point for development workflows.

Can I use natural language to create requirements for a development workflow?▼

Yes, you can use natural language descriptions as input to create and update detailed feature requirements, automating the refinement process for your development workflow.

Do I need an existing spec.md file to update feature requirements?▼

No, you do not need an existing file to start; the process creates the initial spec.md file from your description and can update it as the feature specification evolves.

Related Skills

Explore More Product & Management Skills→
arielybarakarielybarak

speckit-specify

Generate feature specification documents and manage Git branches from natural language descriptions.

Community
Advanced
epieczkoepieczko

epic.decompose

Parse Markdown Epic documents and generate structured user stories as JSON.

Community
Intermediate
tamago0224tamago0224

git-flow-branch-creator

Analyze git status and diff to create Git Flow branches automatically.

Community
Intermediate
panaversitypanaversity
28

stories

Convert specs or PRDs into named-persona user stories with testable acceptance criteria.

Official
Advanced