spec-interview

spec-interview is a skill for Claude Code from cfircoo/claude-code-toolkit. It costs 33 tokens per session (2,310 once invoked), scanned A, original, MIT.

A guided interview tool for turning an idea or feature request into a written project specification. It asks focused questions about requirements, constraints, and assumptions, then saves the result to SPEC.md.

In plain words
What is it for?
Use it when starting a project or feature, reviewing an existing SPEC.md, deciding between design options, and documenting agreed requirements.
Why use it?
It exposes unclear decisions and missing requirements before implementation begins, reducing rework caused by misunderstood goals.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: model in frontmatter.

Good fit Use it when starting a project or feature, reviewing an existing SPEC.md, deciding between design options, and documenting agreed requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cfircoo/claude-code-toolkit/spec-interview
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.

Any agent
npx skills add cfircoo/claude-code-toolkit --skill spec-interview
Clone the repo
git clone --depth 1 https://github.com/cfircoo/claude-code-toolkit

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.

agentmods badge for spec-interview

README.md
[![agentmods](https://agentmods.dev/badge/skills/cfircoo/claude-code-toolkit/spec-interview/github.svg)](https://agentmods.dev/skills/cfircoo/claude-code-toolkit/spec-interview)
Your own site
<a href="https://agentmods.dev/skills/cfircoo/claude-code-toolkit/spec-interview"><img src="https://agentmods.dev/badge/skills/cfircoo/claude-code-toolkit/spec-interview/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.

agentmods 80×15 button for spec-interview

Your own site · 80×15
<a href="https://agentmods.dev/skills/cfircoo/claude-code-toolkit/spec-interview"><img src="https://agentmods.dev/badge/skills/cfircoo/claude-code-toolkit/spec-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,310 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.02310
Opus 5.5 $0.00013 $0.00924
Sonnet 5.5 $0.00007 $0.00462
Haiku 4.5 $0.00003 $0.00231

Measured 1mo ago against content hash c80c39a6a485, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-interview 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.

skills/spec-interview/SKILL.md · 266 lines

How it starts

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

The goal is to surface hidden assumptions and force decisions BEFORE implementation begins.

<essential_principles>

</essential_principles>

<quick_start>

  1. Check if SPEC.md exists and read it
  2. Identify gaps, ambiguities, and untested assumptions
  3. Begin interviewing using AskUserQuestionTool
  4. Cover ALL domains systematically (see question_domains)
  5. Write completed spec to SPEC.md </quick_start>

If exists: Analyze what's defined vs. what's missing or vague. If not: Start fresh, but ask about existing context (related systems, constraints, prior art).

CRITICAL: Each question must:

  • Be specific to THIS project (not generic)
  • Surface a decision or assumption
  • Have meaningful, distinct options
  • Force the user to commit to something

Probe these immediately before moving on.

<question_domains>

Read the full file on GitHub · 266 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 266 lines · 33 tokens per session scan A c80c39a6a485

Subscribe to this mod's changes

spec-interview is a skill published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 2,310 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-08-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens