speckit.specify

Convert natural-language feature descriptions into Speckit specifications.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.specify
Source: https://github.com/lofidonut3/oh-my-speckit/tree/main/skills/speckit.specify
Command: npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit Specify Command Executor streamlines turning natural-language feature descriptions into formal Speckit specifications, enabling teams to define WHAT before diving into design and implementation.

Core Features & Use Cases

  • Automates spec creation: loads the official Speckit /speckit.specify command and executes it within the project context.
  • OpenCode workflow compatibility: reads .opencode/commands/speckit.specify.md and applies syntax transformations ($ARGUMENTS, $1, $2, @filepath, !command).
  • Consistency and governance: preserves handoffs, templates, and standard Speckit conventions for reliable spec generation.
  • Use Case: A product feature described in natural language is converted into a structured spec that can be reviewed, planned, and implemented.

Quick Start

Place the speckit.specify command in .opencode/commands/speckit.specify.md and run the Speckit workflow in your project context to generate a ready-to-validate spec.

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 natural language feature description into a formal specification?

To convert a natural language feature description into a formal specification, you can automate the process by loading and executing the Speckit specify command, which applies syntax rules to generate structured specs and templates from your text.

How does Speckit workflow integration handle command syntax transformations?

Speckit workflow integration handles command syntax transformations by reading the command file and applying specific syntax rules for arguments, file paths, and embedded commands to ensure accurate spec generation within the project context.

Can I use this spec generation approach with OpenCode workflows?

Yes, you can use this spec generation approach with OpenCode workflows. The executor reads the command file directly from the OpenCode commands directory and applies the required syntax transformations for compatibility.

What is the best way to define the WHAT before implementation in software engineering?

The best way to define the WHAT before implementation is to use an automated specification workflow that transforms plain text feature descriptions into structured, reviewable specs, preserving standard conventions and handoffs for reliable planning.

Do I need an existing Speckit setup to generate ready-to-validate specifications?

Yes, you need an existing Speckit setup. The executor requires placing the specify command file in the correct project directory to load the original command, apply syntax rules, and maintain Speckit handoffs and conventions.