What is decision-interview?

A short question-driven command for resolving decisions that are still unclear before implementation rules are written. It focuses on choices that could change behavior, data safety, rollout safety, or testing.

Use it when a task is blocked by unresolved product, technical, safety, or test-strategy choices.

It prevents an agent from silently guessing about important requirements. Asking only high-value questions keeps the decision process focused.

decision-interview — Command for Claude Code by Mozurok/fhorja.dev

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/Mozurok/fhorja.dev

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/mozurok/fhorja.dev/decision-interview/github.svg)](https://agentmods.dev/commands/mozurok/fhorja.dev/decision-interview)

Your own site

<a href="https://agentmods.dev/commands/mozurok/fhorja.dev/decision-interview"><img src="https://agentmods.dev/badge/commands/mozurok/fhorja.dev/decision-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mozurok/fhorja.dev/decision-interview"><img src="https://agentmods.dev/badge/commands/mozurok/fhorja.dev/decision-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 108 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 7,521 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.00108	$0.07521
Opus 5.5	$0.00043	$0.03008
Sonnet 5.5	$0.00022	$0.01504
Haiku 4.5	$0.00011	$0.00752

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

Security

Grade A, and why

decision-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 12d 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.

commands/decision-interview.md · 203 lines

How it starts

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

decision-interview

Act as a senior/staff engineer reducing ambiguity before locking implementation decisions for the active engineering task.

Goal: Ask the minimum set of high-value decision questions needed before turning the task into canonical implementation rules.

Mandatory context bootstrap (before any output):

Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
- ## LLM execution contract
- ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
- ## Global output contract (including Adaptive handoff and Mode selection rule)
- ## Cross-cutting workflow guardrails
Bootstrap tiers: the light-weight commands (branch-commit, what-next, where-we-at, slice-closure, compact-task-memory) plus the high-frequency implement-approved-slice and sync-task-state (v3 wave1 item D) read the four sections above with two subsections of ## Cross-cutting workflow guardrails skipped: ### External web access (centralized) and ### Sequencing heuristics (by phase). Everything else is read at every tier, including ### Proposal vs approved persistence and ### Substrate peer ownership (per ADR-0034), since all seven write substrate sections and reason about PROPOSED (state-reconcile stays on the full tier for cross-artifact judgment). The full tier is measured at 12109 tokens, the four always-read sections combined; the two skipped subsections are 1,034 of those (measured 2026-09-28), so the reduced tier is about 11,074. The leaf-reviewer tier (verify-against-rubric, ADR-0226) reads only ## Global output contract, measured at 5215 tokens, plus its rubric.
Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D): WHEN this conversation already read the bootstrap sections in an earlier turn still VISIBLE in the context window AND WORKFLOW_OPERATING_SYSTEM.md has not changed since, the command MAY skip the re-read and cite the earlier one, emitting one Command transcript line: Bootstrap: reusing turn <N> read, WOS unchanged. Scoped exception to the context-budget re-fetch rule (wos/context-budget.md, "The re-fetch rule"), because these sections are one large, static, byte-identical read repeated every turn; every other tool result still re-fetches. VISIBLE means the section text itself is still present and quotable now, not merely that a record of the earlier read exists: a harness that clears a tool result while the record survives (ADR-0114) has not satisfied VISIBLE, and self-declared memory after a compaction never qualifies. A stateless-per-turn harness is excluded. The transcript line is mandatory; a silent skip is invalid output.
Resolving the spec and wos/<topic>.md: canonical repository FIRST. Otherwise use active-adapter docs: ~/.claude/workflow-docs (CLAUDE_WORKFLOW_DOCS_DIR), ~/.cursor/workflow-docs (WORKFLOW_DOCS_DIR; project .cursor/workflow-docs on project installs), ~/.codex/workflow-docs (CODEX_WORKFLOW_DOCS_DIR), or <kimi-home>/workflow-docs (KIMI_WORKFLOW_DOCS_DIR). Nonempty overrides win. Kimi home: KIMI_CODE_HOME, else existing ~/.kimi-code, else existing ~/.kimi, default ~/.kimi-code. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in ### Command transcript. Installed snapshots refresh and prune retired topics only on sync.
Read additional sections only when relevant to this command's role.
Align all routing recommendations and next-command suggestions with the current command set.
Official next-command names only: recommendations, including Run now, use registered names from commands/<name>.md or commands/<name>/SKILL.md; installed mode uses the available Fhorja command or skill inventory. No invented aliases. Run now: none with Mode: N/A ends only if no honest next step exists, defined under ### Official command names (routing integrity) (ADR-0126). Required inputs:
active task folder path
TASK_STATE.md
SOURCE_OF_TRUTH.md
IMPACT_ANALYSIS.md, if available
INVARIANTS_AND_NON_GOALS.md, if available
DECISIONS.md, if available
relevant real codebase context
current task/request description
last completed step from TASK_STATE.md (command + summary)

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

12d ago Changed · -1 lines · -56 tokens per session daf1e8e8257c
15d ago Changed · -1 lines cc994c37f680
22d ago Changed · -23 lines 6e51ed3659db
23d ago Changed · +30 lines · +18 tokens per session 0f3b1272221c
1mo ago First seen · 198 lines · 146 tokens per session scan A 5320d1c80951

Subscribe to this mod's changes

decision-interview is a command published in the GitHub repository Mozurok/fhorja.dev (10 stars, last pushed 12d ago), licensed MIT. It adds 108 tokens to every session and 7,521 once invoked, about $0.0004 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-03.

Claude Code Planning agent-skills ai-coding cursor developer-tools spec-driven-development

decision-interview

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

decision-interview

What this file has done since we first saw it

Other commands, from other repositories

kiro-steering-custom

constitution

ijfw-execute

ijfw-metrics

specmanager-build

superskill