A command that turns a plain-language feature request into a feature specification. It also creates a short, descriptive name for the related branch after checking existing branches.

Use it to specify features, extract technical terms and keywords, create a two-to-four-word branch name, and check whether a matching branch already exists.

It gives an informal request a consistent structure and naming approach. This makes the planned change easier to discuss and track in version control.

specify — Command for Claude Code by akka/ai-marketplace

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.

Clone the repo

git clone --depth 1 https://github.com/akka/ai-marketplace

Made for: Claude Code.

Or install akka-specify, the plugin that ships this one along with the rest of its 13 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/akka/ai-marketplace/specify/github.svg)](https://agentmods.dev/commands/akka/ai-marketplace/specify)

Your own site

<a href="https://agentmods.dev/commands/akka/ai-marketplace/specify"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/specify/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/akka/ai-marketplace/specify"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 2,686 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 83% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.02686
Opus 5.5	$0.00005	$0.01074
Sonnet 5.5	$0.00003	$0.00537
Haiku 4.5	$0.00001	$0.00269

Measured 1mo ago against content hash c6bdd9912f68, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

Origin

This is a copy

83% identical to specify — 158 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/akka-specify/commands/specify.md · 250 lines

How it starts

The opening of the file, as written. The whole thing — 250 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 /akka-specify: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 branch:
- 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"
Check for existing branches before creating new one:

a. First, fetch all remote branches to ensure we have the latest information.

b. Find the highest feature number across all sources for the short-name:
- Remote branches: git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$'
- Local branches: git branch | grep -E '^[* ]*[0-9]+-<short-name>$'
- Specs directories: Check for directories matching specs/[0-9]+-<short-name>
c. Determine the next available number:
- Extract all numbers from all three sources
- Find the highest number N
- Use N+1 for the new branch number
d. Call the akka_sdd_create_spec MCP tool with feature_name set to a short, hyphenated name derived from the user's feature description (e.g. "user-authentication"). The tool creates a numbered feature directory under the specs directory, initializes spec.md from the template, and returns the path. Use this path as FEATURE_SPEC and its parent directory as FEATURE_DIR.
- Pass number (N+1) and short_name parameters along with the feature description

Read the full file on GitHub · 250 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.

1mo ago First seen · 250 lines · 13 tokens per session scan A c6bdd9912f68

Subscribe to this mod's changes

specify is a command published in the GitHub repository akka/ai-marketplace (7 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 2,686 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to specify, differing in 158 lines, and is treated as a copy.

Claude Code Planning ai akka gemini-ai spec-driven-development

autospec.plan

Generate YAML implementation plan from feature specification.

ariel-frischer/autospec · 8 tokens

cc-review

(Conductor) Review code changes against spec and standards.

yeisonrestrepo/code-conductor · 11 tokens

wayfind

Plan a chunk of work too big for one agent session as a shared decision map: map.md + typed decision tickets in the mega-goal folder, resolved one per session through the kit's own grill/prototype/research machinery, until nothing is left to decide. Then hand off to /kit:spec or a ROADMAP, never straight to execute.

dwarvesf/dwarves-kit · 71 tokens

specify