A clarification and planning command for tasks that are not yet well defined. It asks questions about scope, success, and technical context, then waits for answers before producing an implementation plan.

Use it at the start of an ambiguous feature or change when the desired behaviour, affected area, or definition of done needs to be agreed first.

It prevents code from being written against unclear requirements or assumptions. It uses the repository to answer questions that can be resolved from the code instead of asking the user unnecessarily.

How ikhanux/ai-coding-blueprint configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ikhanux/ai-coding-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ikhanux/ai-coding-blueprint/main/.claude/commands/clarify.md

Clone the repo

git clone --depth 1 https://github.com/ikhanux/ai-coding-blueprint

Made for: Claude Code.

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/ikhanux/ai-coding-blueprint/clarify/github.svg)](https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/clarify)

Your own site

<a href="https://agentmods.dev/commands/ikhanux/ai-coding-blueprint/clarify"><img src="https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/clarify/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/ikhanux/ai-coding-blueprint/clarify"><img src="https://agentmods.dev/badge/commands/ikhanux/ai-coding-blueprint/clarify.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 326 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 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.1	$0.00013	$0.00326
Opus 5.5	$0.00005	$0.00130
Sonnet 5.5	$0.00003	$0.00065
Haiku 4.5	$0.00001	$0.00033

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

.claude/commands/clarify.md · 41 lines

What it actually says

Task: $ARGUMENTS

Do not implement yet.

1. Clarify

Interview the user about this task until you share an understanding of it. Walk down the design tree: each answer opens the next question, and dependencies between decisions get resolved one at a time rather than all at once. Ask at least 3 questions covering scope, success criteria, and technical context; if anything is still unclear after that, keep going. Don't cap it.

Rules for the questions:

If the codebase can answer it, don't ask. Read the code (or send Explore) and state what you found instead.
Give your recommended answer with every question, and why. The user should be choosing, not generating.
Ground them in this repo: which feature area and actor from .ai/PROJECT.md the work belongs to, which existing file or pattern it should follow, what "done" looks like when the user tries it. Add examples and edge cases so the intent is unambiguous.
No filler, no yes/no questions, nothing the task already answers.

Stop and wait for the answers.

2. Plan

After the answers, give:

Restated task (1-2 sentences)
Numbered steps, concrete and executable (file paths, names)
Assumptions for anything left ambiguous
Risks / open questions

Wait for confirmation before writing any code.

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 · 41 lines · 13 tokens per session scan A eda1de7475be

Subscribe to this mod's changes

clarify is a command published in the GitHub repository ikhanux/ai-coding-blueprint (2 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 326 once invoked, about $0.0001 per session on Opus 5.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-09-21.

Planning

clarify next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
clarifyikhanux/ai-coding-blueprint	Command	2	1mo ago	MIT	A	13	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

ai-coding-blueprint: Command for Claude Code