# Requirement Clarification > Guidelines for asking clarifying questions when requirements are ambiguous. Use when scope is unclear, multiple approaches exist, or critical details are missing. Use when this capability is needed. - Skill: `tomevault-io/requirement-clarification` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/requirement-clarification` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/requirement-clarification/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/requirement-clarification --- # requirement-clarification ## Quick Start 1. Identify ambiguity -> Formulate specific questions -> Ask before implementing 2. Ask about scope, edge cases, and trade-offs when unclear 3. Propose options with trade-offs when multiple approaches exist 4. Never assume - verify critical decisions with user ## Key Principles - **Ask early**: Clarify before writing code, not after - **Be specific**: Ask targeted questions, not vague ones - **Offer options**: Present 2-3 approaches with trade-offs - **Batch questions**: Group related questions together - **Know when NOT to ask**: Skip for trivial/obvious decisions ## When to Ask - Multiple valid implementations exist - Business logic implications unclear - Scope boundaries undefined - Breaking changes possible - Security/performance trade-offs involved ## References See [rules.md](references/rules.md) for question templates and anti-patterns. --- > Source: [eser/aya.is](https://github.com/eser/aya.is) — distributed by [TomeVault](https://tomevault.io).