speckit-specify

Convert natural language feature descriptions into software specifications.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-specify-apothecaryman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/speckit-specify
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-specify-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of feature specifications from natural language feature descriptions, streamlining the process for software development projects.

Core Features & Use Cases

  • Natural Language Processing: Converts feature descriptions into concise specifications.
  • Compatibility Check: Ensures the project structure meets the required spec-kit project structure.
  • Branch Creation: Optionally creates a git branch for the new feature specification.
  • Spec File Generation: Creates a spec file with a predefined template.
  • Quality Validation: Validates the specification against quality criteria.
  • Extension Hooks: Allows for optional and mandatory extension hooks to enhance functionality.
  • Use Case: Ideal for teams that need to quickly draft feature specifications from user requirements without manual writing.

Quick Start

Run the 'speckit-specify' command with a feature description to generate a specification.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I convert natural language descriptions into software specifications?

To convert natural language descriptions into software specifications, use this Skill to parse feature requirements and automatically generate structured spec files within a spec-kit project, validating them against predefined quality criteria.

Do I need a spec-kit project structure to generate feature specifications?

Yes, you need a spec-kit project structure with a .specify/ directory to generate feature specifications, as the Skill relies on YAML parsing and git operations within this environment to create and validate spec files.

Can I automatically create a git branch when drafting a new feature specification?

Yes, you can automatically create a git branch when drafting a new feature specification, as the Skill integrates git operations to optionally branch your repository before generating the spec file from your natural language input.

What's the best way to validate feature specifications against quality criteria?

The best way to validate feature specifications against quality criteria is to use this Skill's built-in validation, which checks your generated spec files against predefined standards to ensure completeness and consistency.

Does this tool work with YAML for software development specification generation?

Yes, this tool works with YAML for software development specification generation, utilizing YAML parsing to process configurations and generate structured spec files from your natural language feature descriptions.

What are the limitations of automated feature specification from natural language?

Limitations of automated feature specification from natural language include strict dependency on the spec-kit project structure and .specify/ directory, requiring valid YAML configurations and git integration to function properly.