speckit-specify
Create or update the feature specification from a natural language feature description.
github-spec-kit · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add acryldev/acryl --skill speckit-specifyAbout this skill
name: "speckit-specify" description: "Create or update the feature specification from a natural language feature description." compatibility: "Requires spec-kit project structure with .specify/ directory" metadata: author: "github-spec-kit" source: "templates/commands/specify.md"
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before specification):
- Check if
.specify/extensions.ymlexists in the project root. - If it exists, read it and look for entries under the
hooks.before_specifykey - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabledis explicitlyfalse. Treat hooks without anenabledfield as enabled by default. - For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
- When constructing slash commands from hook command names, replace dots (
.) with hyphens (-). For example,speckit.git.commit→/speckit-git-commit. - For each executable hook, output the following based on its
optionalflag:- Optional hook (
optional: true):## Extension Hooks **Optional Pre-Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}` - Mandatory hook (
optional: false):
After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal## Extension Hooks **Automatic Pre-Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command} Wait for the result of the hook command before proceeding to the Outline.{command}id shown above, e.g. a skills-mode agent runs it as/skill:speckit-...or$speckit-...). Emitting the block alone does not run the hook.
- Optional hook (
- If no hooks are registered or
.specify/extensions.ymldoes not exist, skip silently
Outline
The text the user typed after /speckit-specify in the triggering message is the feature description. Assume you always have it available in this conversation even if $ARGUMENTS appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that feature description, do this:
-
Generate a concise short name (2-4 words) for the feature:
- Analyze the feature description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the feature
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Keep it concise but descriptive enough to understand the feature at a glance
- Examples:
- "I want to add user authentication" → "user-auth"
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
- "Create a dashboard for analytics" → "analytics-dashboard"
- "Fix payment processing timeout bug" → "fix-payment-timeout"
-
Branch creation (optional, via hook):
If a
before_specifyhook ran successfully in the Pre-Execution Checks above, it will have created/switched to a git branch and output JSON containingBRANCH_NAMEandFEATURE_NUM. Note these values for reference, but the branch name does not dictate the spec directory name.If the user explicitly provided
GIT_BRANCH_NAME, pass it through to the hook so the branch script uses the exact value as the branch name (bypassing all prefix/suffix generation). -
Create the spec feature directory:
Specs live under the default
specs/directory unless the user explicitly providesSPECIFY_FEATURE_DIRECTORY.Resolution order for
SPECIFY_FEATURE_DIRECTORY:- If the user explicitly provided
SPECIFY_FEATURE_DIRECTORY(e.g., via environment variable, argument, or configuration), use it as-is - Otherwise, auto-generate it under
specs/:- Check
.specify/init-options.jsonforfeature_numbering(preferred) orbranch_numbering(deprecated, migration only — will be removed in a future release) - If
"timestamp": prefix isYYYYMMDD-HHMMSS(current timestamp) - If
"sequential"or absent: prefix isNNN(next available 3-digit number after scanning existing directories inspecs/) - Construct the directory name:
<prefix>-<short-name>(e.g.,003-user-author20260319-143022-user-auth) - Set
SPECIFY_FEATURE_DIRECTORYtospecs/<directory-name> - If
branch_numberingwas used (andfeature_numberingwas absent), emit a one-line warning: "⚠️branch_numberingin init-options.json is deprecated. Rename tofeature_numbering."
- Check
Create the directory and spec file:
mkdir -p SPECIFY_FEATURE_DIRECTORY- Resolve the active
spec-templatethrough the Spec Kit preset/template resolution stack (equivalent tospecify preset resolve spec-template) - Copy the resolved
spec-templatefile toSPECIFY_FEATURE_DIRECTORY/spec.mdas the starting point - Set
SPEC_FILEtoSPECIFY_FEATURE_DIRECTORY/spec.md - Persist the resolved path to
.specify/feature.json:
Write the actual resolved directory path value (for example,{ "feature_directory": "<resolved feature dir>" }specs/003-user-auth), not the literal stringSPECIFY_FEATURE_DIRECTORY. This allows downstream commands (/speckit-plan,/speckit-tasks, etc.) to locate the feature directory without relying on git branch name conventions.
IMPORTANT:
- If the user explicitly provided