A feature-specification helper that fills in unclear details from existing project decisions, documentation, or code patterns, and asks about only the choices that genuinely need a decision.

Use it to resolve missing requirements before creating a technical plan and implementation tasks.

It reduces back-and-forth during planning and records automatic assumptions so they can be reviewed later.

clarify — Command by MartyBonacci

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/clarify

Clone the repo

git clone --depth 1 https://github.com/MartyBonacci/specswarm

Or install ss, the plugin that ships this one along with the rest of its 10 skills, 34 commands, 6 agents, 4 hooks.

Per session 77 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,560 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.

Model	Per session	Once invoked
Fable 5	$0.00077	$0.05560
Opus 5	$0.00039	$0.02780
Sonnet 5	$0.00015	$0.01112
Haiku 4.5	$0.00008	$0.00556

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

Security

Grade A, and why

clarify 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 3d 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/clarify.md · 362 lines

How it starts

The opening of the file, as written. The whole thing — 362 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

Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.

Assume-first principle (v7.13.0): every detected gap is classified three ways before it is allowed to become a question:

(a) Resolvable from the taste model (distilled feedback_*.md rulings in the memory dirs) → AUTO-FILL, cite the entry by name.
(b) Resolvable from the spec corpus or codebase precedent → AUTO-FILL, cite the corpus section or file:line of the precedent.
(c) Genuine fork — no precedent, materially different outcomes → question, batched with the other forks.

Auto-fills are recorded in the spec's ## Assumptions section with per-entry provenance, reviewable like a diff. Only class (c) reaches the user. Origin lesson: reviewing assumptions is ~5× faster than answering questions; a 10-gap spec with a populated taste model should yield ≤3 questions.

Note: This clarification workflow is expected to run (and be completed) BEFORE invoking /speckit.plan. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.

Execution steps:

Discover Feature Context:

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
get_features_dir "$REPO_ROOT"

BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
FEATURE_NUM=$(echo "$BRANCH" | grep -oE '^[0-9]{3}')
[ -z "$FEATURE_NUM" ] && FEATURE_NUM=$(list_features "$REPO_ROOT" | grep -oE '^[0-9]{3}' | sort -nr | head -1)

find_feature_dir "$FEATURE_NUM" "$REPO_ROOT"
# FEATURE_DIR is now set by find_feature_dir
FEATURE_SPEC="${FEATURE_DIR}/spec.md"

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

3d ago First seen · 362 lines · 77 tokens per session scan A 68e7c74d71d6

Subscribe to this mod's changes

clarify is a command published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 5,560 once invoked, about $0.0004 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.

Planning

clarify

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

User Input

Outline

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

converge