How do I install the Speckit Specify skill?

Run npx skillmds@latest add tomevault-io/speckit-specify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Speckit Specify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Speckit Specify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Speckit Specify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Speckit Specify?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Speckit Specify by tomevault-io — Agent Skill

Name: Speckit Specify
Author: tomevault-io

Speckit Specify

Create or update the feature specification from a natural language feature description. Use when defining WHAT a feature should do before any design or implementation work. Use when this capability is needed.

tomevault-io a50bee5 2 files · 2.7 KB Updated Sep 17, 2026

File contents

Speckit Specify Command Executor

This skill executes the official GitHub Speckit /speckit.specify command.

Execution Protocol

When this skill is invoked, you MUST:

1. Load the Original Command File

Read and parse .opencode/commands/speckit.specify.md from the current project directory.

2. Process OpenCode Command Syntax

The command file uses special syntax that MUST be processed before execution:

Syntax	Action
`$ARGUMENTS`	Replace with user-provided arguments (the feature description)
`$1`, `$2`, etc.	Replace with positional arguments
`@filepath`	Read the file at `filepath` and insert its full contents
`!`command``	Execute the shell command and insert its stdout

3. Execute the Processed Instructions

After syntax processing, follow all instructions in the command file exactly as written, including:

Running .specify/scripts/powershell/create-new-feature.ps1 as specified
Reading .specify/templates/spec-template.md for structure
Creating the spec file at the designated location
Creating quality validation checklist

4. Maintain Speckit Workflow Integrity

Honor the handoffs defined in the command's YAML frontmatter
Suggest /speckit.clarify or /speckit.plan as next steps
Preserve all Speckit conventions (branch naming, file paths, structure)

User Input

$ARGUMENTS

Fallback

If .opencode/commands/speckit.specify.md does not exist, check for:

.opencode/command/speckit.specify.md (legacy path)

If no command file is found, report an error and suggest running specify init first.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: speckit-specifydescription: Create or update the feature specification from a natural language feature description. Use when defining WHAT a feature should do before any design or implementation work. Use when this capability is needed.---# Speckit Specify Command Executor**This skill executes the official GitHub Speckit `/speckit.specify` command.**## Execution ProtocolWhen this skill is invoked, you MUST:### 1. Load the Original Command FileRead and parse `.opencode/commands/speckit.specify.md` from the current project directory.### 2. Process OpenCode Command SyntaxThe command file uses special syntax that MUST be processed before execution:| Syntax | Action ||--------|--------|| `$ARGUMENTS` | Replace with user-provided arguments (the feature description) || `$1`, `$2`, etc. | Replace with positional arguments || `@filepath` | Read the file at `filepath` and insert its full contents || `!`command`` | Execute the shell command and insert its stdout |### 3. Execute the Processed InstructionsAfter syntax processing, follow all instructions in the command file **exactly as written**, including:- Running `.specify/scripts/powershell/create-new-feature.ps1` as specified- Reading `.specify/templates/spec-template.md` for structure- Creating the spec file at the designated location- Creating quality validation checklist### 4. Maintain Speckit Workflow Integrity- Honor the `handoffs` defined in the command's YAML frontmatter- Suggest `/speckit.clarify` or `/speckit.plan` as next steps- Preserve all Speckit conventions (branch naming, file paths, structure)## User Input```text$ARGUMENTS```## FallbackIf `.opencode/commands/speckit.specify.md` does not exist, check for:- `.opencode/command/speckit.specify.md` (legacy path)If no command file is found, report an error and suggest running `specify init` first.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lofidonut3) — claim your Tome and manage your conversions.

Frequently asked questions