ask-questions-if-underspecified

Clarify underspecified requests by asking must-have questions before implementation.

1|Updated Feb 5, 2026

Search Tags:#workflow #planning #requirements #safety #questioning #clarify

Ready to run

npx skills add https://github.com/jandragsbaek/codex-template --skill ask-questions-if-underspecified

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/jandragsbaek/codex-template/tree/main/.codex/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/jandragsbaek/codex-template --skill ask-questions-if-underspecified

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill clarifies requirements before implementing to prevent incorrect outcomes.

Core Features & Use Cases

Clarify before action: prompts for concise, must-have questions to resolve ambiguity.
Plan mode when needed: evaluates the scope or risk and suggests a planning step before work begins.
Safe progression: pauses work until explicit user confirmation or given defaults are agreed.

Quick Start

Read the docs with scripts/docs-list before anything else. Identify missing objectives, acceptance criteria, or constraints, and ask 1–5 must-have questions. If multiple subsystems, high risk, or unclear effort is detected, propose a concise plan and await user confirmation before proceeding.

Frequently Asked Questions about ask-questions-if-underspecified

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I clarify software requirements before starting implementation?▼

Clarifying requirements before implementation involves identifying missing objectives, constraints, or environment details, then prompting concise must-have questions. This prevents incorrect outcomes by ensuring scope is fully defined before any work begins.

When should I use a plan mode for software development workflows?▼

You should use a plan mode when evaluating scope or risk reveals multiple subsystems, high risk, or unclear effort. It proposes a concise planning step to define the work structure before execution, pausing until you provide explicit confirmation to proceed safely.

What is the best way to prevent incorrect work from ambiguous project requests?▼

The best way to prevent incorrect work from ambiguous requests is to target undetermined aspects across scope, constraints, and environment. By pausing to ask must-have questions and awaiting explicit confirmation, you enforce safe, stepwise execution before proceeding.

How do you ensure safe stepwise execution when planning new features?▼

You ensure safe stepwise execution by reading the relevant documentation first, identifying missing constraints, and pausing work for user answers. You proceed only after receiving explicit confirmation or agreeing on given defaults for the requirements.

Does clarifying requirements before acting work for complex multi-subsystem environments?▼

Yes, clarifying requirements works for complex environments. When multiple subsystems or high risk are detected, it automatically suggests a planning step to evaluate scope, ensuring safe progression by pausing for explicit user confirmation before implementation.