specify

A command that creates or updates a written specification for a software feature from a natural-language description.

In plain words
What is it for?
Use it to initialize the feature structure, assign a feature number, create a URL-like feature name, and record the requested behavior.
Why use it?
It turns an informal feature idea into a consistent specification that can guide later development.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/martybonacci/specswarm/specify
Clone the repo
git clone --depth 1 https://github.com/MartyBonacci/specswarm
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,635 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.05635
Opus 5 $0.00006 $0.02818
Sonnet 5 $0.00003 $0.01127
Haiku 4.5 $0.00001 $0.00564

Measured 2d ago against content hash 7c9a32f82549, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

specify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/ss/commands/specify.md · 544 lines

How it starts

The opening of the file, as written. The whole thing — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

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 {ARGS} appears literally below. Do not ask the user to repeat it unless they provided an empty command.

Given that feature description, do this:

  1. Create New Feature Structure (replaces script execution):

    a. Find Repository Root and Initialize Features Directory:

    REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
    
    # Source features location helper
    SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
    PLUGIN_DIR="$(dirname "$SCRIPT_DIR")"
    source "$PLUGIN_DIR/lib/features-location.sh"
    
    # Initialize features directory (handles migration if needed)
    ensure_features_dir "$REPO_ROOT"
    

    b. Determine Next Feature Number:

    # Get next feature number using helper
    FEATURE_NUM=$(get_next_feature_number "$REPO_ROOT")
    

    c. Create Feature Slug from Description:

    # Convert description to kebab-case
    # Example: "User Authentication System" → "user-authentication-system"
    SLUG=$(echo "$ARGUMENTS" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-//' | sed 's/-$//')
    

    d. Capture Parent Branch and Create Feature Branch (if git available):

    BRANCH_NAME="${FEATURE_NUM}-${SLUG}"
    
    if git rev-parse --git-dir >/dev/null 2>&1; then
      # Check if already on a feature branch (e.g., created by /ss:build)
      CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
      ALREADY_ON_FEATURE=$(echo "$CURRENT_BRANCH" | grep -E '^[0-9]{3}-')
    
      if [ -n "$ALREADY_ON_FEATURE" ]; then
        # Already on a feature branch - reuse it
        BRANCH_NAME="$CURRENT_BRANCH"
        FEATURE_NUM=$(echo "$CURRENT_BRANCH" | grep -oE '^[0-9]{3}')
        # Read parent from build state if available
        PARENT_BRANCH=""
        if [ -f "${REPO_ROOT}/.specswarm/build-loop.state" ] && command -v jq &>/dev/null; then
          PARENT_BRANCH=$(jq -r '.parent_branch // empty' "${REPO_ROOT}/.specswarm/build-loop.state" 2>/dev/null)
        fi
        if [ -z "$PARENT_BRANCH" ]; then
          PARENT_BRANCH="main"
        fi
        echo "Using existing feature branch: $BRANCH_NAME (parent: $PARENT_BRANCH)"
      else
        # Standalone mode: create new feature branch with confirmation
        PARENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
    
        echo ""
        echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
        echo "Branch Setup"
        echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
        echo "  Parent branch: $PARENT_BRANCH (current branch)"
        echo "  Feature branch: $BRANCH_NAME (will be created)"
        echo ""
        echo "ℹ️  The feature branch will be created from $PARENT_BRANCH."
        echo "   When complete, it will merge back to $PARENT_BRANCH."
        echo ""
        read -p "Is this correct? (y/n): " branch_confirm
    
        if [ "$branch_confirm" != "y" ]; then
          echo ""
          echo "❌ Branch setup cancelled"
          echo ""
          echo "Please checkout the correct parent branch first, then run:"
          echo "  /ss:specify \"$FEATURE_DESCRIPTION\""
          exit 0
        fi
        echo ""
    
        # Create and switch to new feature branch
        git checkout -b "$BRANCH_NAME"
      fi
    else
      # Non-git: use environment variable
      export SPECIFY_FEATURE="$BRANCH_NAME"
      PARENT_BRANCH="unknown"
    fi
    

Read the full file on GitHub · 544 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 544 lines · 13 tokens per session scan A 7c9a32f82549

Subscribe to this mod's changes

specify is a command published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 5,635 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.