speckit-specify

Convert natural language feature ideas into GitHub Issue-backed specs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ranvirsingh/speckit --skill speckit-specify-ranvirsingh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/ranvirsingh/speckit/tree/main/skills/speckit-specify
Command: npx skills add https://github.com/ranvirsingh/speckit --skill speckit-specify-ranvirsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Create or update a feature specification, bug report, or chore definition as a GitHub Issue-backed spec from a natural language description. Use this skill when the user wants to define a new feature, report a bug, write requirements, capture user stories, or create a spec. Triggers on requests like "I want to build...", "specify a feature for...", "write a spec", "fix this bug", or any feature ideation, bug reporting, and scoping task.

Core Features & Use Cases

  • Create or update a feature specification, bug report, or chore definition as a GitHub Issue-backed spec from natural language descriptions.
  • Trigger on user commands to generate a structured spec, attach it to a GitHub Issue, and preserve the original description for traceability.
  • Integrate with next steps via plan and retro workflows, ensuring the spec remains the canonical source of truth in the Issue body.

Quick Start

Use this skill by providing a natural-language feature or issue description; it will generate an issue-backed spec in your GitHub repository.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I convert a vague feature idea into a structured GitHub Issue spec?▼

To convert a feature idea into a GitHub Issue spec, provide a natural language description. The tool generates a structured spec, attaches it to a GitHub Issue, and preserves the original description for traceability.

What is the best way to write requirements and user stories from natural language?▼

Writing requirements and user stories from natural language involves generating an issue-backed spec. The tool triggers on feature ideation requests, runs interactive clarification rounds to gather details, and outputs a canonical spec.

Can I use this to scope a bug report and attach it directly to a GitHub Issue?▼

Yes, you can scope a bug report and attach it to a GitHub Issue. The tool processes bug reporting tasks by generating a structured spec from your natural language input and placing it in the GitHub Issue body.

Does generating an issue-backed spec require manual formatting of the GitHub Issue body?▼

Generating an issue-backed spec does not require manual formatting. The tool automatically creates the structured spec, coordinates with follow-on plan and retro workflows, and ensures the spec resides canonically in the GitHub Issue body.

How does interactive clarification help when defining a feature specification?▼

Interactive clarification helps define a feature specification by prompting for essential details during generation. This process turns vague feature ideas into concrete, issue-backed specs by resolving ambiguities before creating the GitHub Issue.