skills.rest
bytes032
bytes032COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ask-questions-if-underspecified

Identify underspecified requests and prompt for must-have clarifying questions before implementation.

Updated Aug 27, 2026
Search Tags:#workflow#requirements#product-management#questioning#clarify#underspecified
One-click install
npx skills add https://github.com/bytes032/agentkit --skill ask-questions-if-underspecified-bytes032
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/bytes032/agentkit/tree/main/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/bytes032/agentkit --skill ask-questions-if-underspecified-bytes032

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify requirements before implementing to prevent work on underspecified requests.

Core Features & Use Cases

  • Structured questioning workflow that surfaces must-have questions.
  • Quick alignment on scope, objectives, constraints, and acceptance criteria.
  • Templates and prompts to guide users in formulating concise, answerable questions.

Quick Start

Ask the must-have clarifying questions before starting any implementation.

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 underspecified requirements before starting product or engineering work?▼

You can clarify underspecified requirements by triggering a deterministic questioning workflow that pauses before action, prompting you with compact, answerable questions to align on scope, objectives, constraints, and acceptance criteria before implementation starts.

What are must-have clarifying questions for product management and design tasks?▼

Must-have clarifying questions target unclear objectives, scope, constraints, and acceptance criteria. They guide user decisions using compact, answerable prompts to ensure complete alignment before any product, engineering, or design implementation starts.

How do I prevent working on underspecified requests in a project workflow?▼

Prevent working on underspecified requests by implementing pause-before-action guards. This mechanism identifies unclear requests and forces a structured questioning phase to establish safe defaults and gather necessary criteria before execution.

Does this requirements clarification approach work for engineering and design tasks?▼

Yes, clarifying requirements applies directly to product, engineering, and design tasks. It identifies unclear objectives and constraints, using a deterministic workflow to prompt must-have questions and establish safe defaults before implementation.

What is the best way to align on acceptance criteria when a request is unclear?▼

The best way to align on acceptance criteria is using a deterministic questioning workflow with safe-default prompts. It surfaces compact, answerable questions to quickly resolve ambiguities in scope and constraints before acting.

Related Skills

Explore More Product & Management Skills→
ibnuhalimmibnuhalimm

Architect

Gather project context and produce a detailed architecture plan.

Community
Advanced
realsigridjinrealsigridjin
20

ralph-init

Create a structured Product Requirements Document from a project description.

Community
Intermediate
mguilarduccimguilarducci
1

brainstorm

Facilitates Phase 1 brainstorming and design exploration for complex tasks.

Community
Advanced
hb9397hb9397

design-doc

Generate structured design documents and PRDs from raw project inputs.

Community
Advanced