speckit-specify

Convert natural language feature descriptions into formal specifications with git branching.

1|1|Updated May 31, 2026
One-click install
npx skills add https://github.com/WayneSHC/polaris-desk --skill speckit-specify-wayneshc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/WayneSHC/polaris-desk/tree/main/.claude/skills/speckit-specify
Command: npx skills add https://github.com/WayneSHC/polaris-desk --skill speckit-specify-wayneshc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spec-kit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of manually writing detailed feature specifications, providing a way to create or update feature specifications directly from natural language feature descriptions.

Core Features & Use Cases

  • Natural Language to Spec: Convert natural language descriptions into formal feature specifications.
  • Automated Branching: Optional feature for creating or switching to a git branch based on feature specification.
  • Feature Directory Creation: Generates a dedicated directory for the feature specification within the project structure.
  • Spec File Initialization: Initializes a spec file using a predefined template with necessary sections.

Quick Start

To create a new feature specification, run the /speckit-specify command with your feature description.

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 for agile development?

To generate feature specifications from natural language, you can use automated tools that transform text descriptions into formal specs. This Skill converts plain language input into structured specification files and initializes dedicated feature directories within your project.

Can I automate git branching when creating a new feature specification?

Yes, you can automate git branching when creating a feature specification. This Skill optionally creates a new git branch or switches to an existing one based on the feature specification, streamlining agile development workflows.

What is the best way to convert plain text feature ideas into formal specifications?

The best way to convert plain text feature ideas into formal specifications is using a template-based generator. This Skill initializes spec files with predefined necessary sections, ensuring consistent structure from natural language feature descriptions.

Do I need spec-kit to manage feature development workflow with natural language specs?

Yes, you need spec-kit as a dependency to manage feature development workflow with natural language specs. The Skill relies on spec-kit to handle directory creation, template-based specification generation, and feature workflow management.

Does this specification generator work with existing project directory structures?

The specification generator works with existing project structures by creating a dedicated directory for the feature specification. It integrates into your current project environment to manage feature development workflow without disrupting established layouts.

Why use template-based specification generation for feature development instead of manual writing?

Template-based specification generation eliminates the challenge of manually writing detailed feature specs. It standardizes spec file initialization with necessary sections, ensuring consistent formal specifications directly from natural language descriptions for agile collaboration.