skills.rest
jineyne
jineyneCOMMUNITY
Explore all skills by this author →
GitHub

speckit-specify

Generate a SPEC.md feature specification from natural language descriptions.

Updated Apr 4, 2026
Search Tags:#workflow#planning#templates#specification#requirements#feature
One-click install
npx skills add https://github.com/jineyne/qt-mcp --skill speckit-specify-jineyne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/jineyne/qt-mcp/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/jineyne/qt-mcp --skill speckit-specify-jineyne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms vague feature ideas into a complete, decision-ready specification that teams can plan from.

Core Features & Use Cases

  • Generate a structured SPEC.md from a natural language feature description using a defined template.
  • Capture user goals, scope boundaries, success criteria, and acceptance scenarios in clear, testable terms.
  • Update an existing SPEC.md to reflect new requirements or clarified decisions based on evolving input.

Quick Start

Provide a concise feature description to instantly produce a ready-to-use specification document.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I generate a feature specification from a natural language description?▼

You can update an existing SPEC.md by providing evolving input or clarified decisions. The tool adjusts the feature specification to reflect new requirements while maintaining the standard template structure.

What should a complete feature specification include for team planning?▼

A complete feature specification should capture user goals, scope boundaries, success criteria, and acceptance scenarios in clear, testable terms. It also documents assumptions to create a decision-ready document.

How do I write testable acceptance criteria for feature requirements?▼

Testable acceptance criteria are generated by translating natural language feature descriptions into structured user scenarios. The tool ensures these scenarios are documented in clear, testable terms within the SPEC.md.

Can I update an existing SPEC.md to reflect new requirements?▼

To generate a feature specification, provide a concise natural language feature description. The tool identifies scope, user scenarios, requirements, and acceptance criteria, outputting a complete SPEC.md and branch information.

What is the best way to turn vague feature ideas into decision-ready specs?▼

The best way to turn vague feature ideas into decision-ready specs is to use a standard template that identifies scope, user scenarios, and acceptance criteria. This outputs a consistent, machine-readable SPEC.md path and branch information.

Does the generated feature specification include branch information?▼

Yes, the generated feature specification includes associated branch information. It outputs both the path to the SPEC.md and the branch details in a consistent, machine-readable format.

Related Skills

Explore More Product & Management Skills→
Rubiss-ProjectsRubiss-Projects
25

speckit-specify

Generate feature specifications from natural language descriptions.

Official
Advanced
alexandersumeralexandersumer
1

clear-merge-blockers

Identify and resolve merge blockers in code repositories with CI/CD integration.

Community
Advanced
troykellytroykelly
11

issue-prerequisite

Create or validate GitHub issues with acceptance criteria and project board links.

Community
Advanced
GustavoGutierrezGustavoGutierrez

acceptance-criteria-generator

Generate Gherkin Given/When/Then acceptance criteria from user stories.

Community
Intermediate