What is define-questions?

A command that reads a document and extracts its questions, open decisions, unclear areas, and incomplete sections into a downloadable JSON or CSV file. JSON is structured data commonly used by programs, while CSV is a simple table format.

Use it to prepare questions from requirements, specifications, and planning documents, with optional previews and formats suited to people or scripts.

It turns scattered unfinished points into a reviewable list, making it easier to answer them or pass them to another workflow.

define-questions — Command for Claude Code by davistroy

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/davistroy/claude-marketplace

Made for: Claude Code.

Or install personal-plugin, the plugin that ships this one along with the rest of its 29 skills, 23 commands, 10 agents, 2 hooks.

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/davistroy/claude-marketplace/define-questions/github.svg)](https://agentmods.dev/commands/davistroy/claude-marketplace/define-questions)

Your own site

<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/define-questions"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/define-questions/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/davistroy/claude-marketplace/define-questions"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/define-questions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 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,877 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.00009	$0.02877
Opus 5	$0.00005	$0.01438
Sonnet 5	$0.00002	$0.00575
Haiku 4.5	$0.00001	$0.00288

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

Security

Grade A, and why

define-questions 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.

plugins/personal-plugin/commands/define-questions.md · 308 lines

How it starts

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

Define Questions Command

Analyze the document specified by the user and extract all questions, open items, areas needing clarification, and incomplete sections into a comprehensive, downloadable JSON file.

Pipeline component: This command extracts questions to JSON. For the combined extract → answer → update workflow, use /finish-document.

Input Validation

Required Arguments:

<document-path> - Path to the document to analyze

Optional Arguments:

--format [json|csv] - Output format (default: json)
- json: Structured format with metadata (default, compatible with /ask-questions)
- csv: Flat tabular format with columns: id, text, context, topic, sections, priority
--preview - Show summary and ask for confirmation before saving
--force - Save output even if schema validation fails (not recommended)
--no-prompt - Disable interactive prompting for missing arguments (for scripts and CI/CD)

Validation: If the document path is missing:

If --no-prompt is specified, display the error and exit:

Error: Missing required argument

Usage: /define-questions <document-path> [--format json|csv] [--no-prompt]
Example: /define-questions PRD.md
Example: /define-questions docs/requirements.md
Example: /define-questions PRD.md --format csv

Otherwise (default), prompt interactively:

/define-questions requires a document path.

Please provide the path to the document to analyze:
> _

(or use --no-prompt to disable interactive prompting)

Wait for the user to provide the document path, then proceed with analysis.

Instructions

Read the specified document - The user will provide a document path or name after the /define-questions command (e.g., /define-questions PRD.md). Read and analyze that document thoroughly.
Identify all questions and open items - Look for:
- Explicit questions (sentences ending with ?)
- Open items marked with "TBD", "TODO", "TBC", or similar markers
- Incomplete sections or placeholders
- Areas marked as needing review or decision
- Gaps in specifications or requirements
- Ambiguous or vague statements that need clarification
- Missing details that would be needed for implementation
- Dependencies or prerequisites that are undefined
- Edge cases or scenarios not addressed

Read the full file on GitHub · 308 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 First seen · 308 lines · 9 tokens per session scan A 56eb95bba511

Subscribe to this mod's changes

define-questions is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 2,877 once invoked, about $0.0000 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-31.

Documents

brand-generate

Generate an on-brand document from a saved Brand Profile.

ferdinandobons/brand-docs · 0 tokens

prose-review-docs

Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…

ihudak/ihudak-claude-plugins · 67 tokens

define-questions

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

Define Questions Command

Input Validation

Instructions

What this file has done since we first saw it

Other commands, from other repositories

brand-generate

prose-review-docs

cti-report

ppt-image2-editable-rebuild

render-figures

harness-onboarding