clarify-first

Prompt targeted clarifying questions to resolve information gaps before implementation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Mrlyk/SKILLS --skill clarify-first-mrlyk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify-first
Source: https://github.com/Mrlyk/SKILLS/tree/main/skills/clarify-first
Command: npx skills add https://github.com/Mrlyk/SKILLS --skill clarify-first-mrlyk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before taking action, identify all unknowns and force clarifying questions until every uncertainty is resolved, to prevent scope creep and rework.

Core Features & Use Cases

  • Exploration phase: Inspect the project context, repository structure, and related documents to surface unknowns.
  • Uncertainty scanning: Systematically list information gaps across business logic, data, interfaces, and external dependencies.
  • Iterative questioning workflow: Group uncertainties by priority and conduct iterative rounds with at most two questions per round, until all points are addressed.
  • Decision to proceed: Upon confirmation, proceed with implementation with a clear, user-aligned plan.

Quick Start

Begin by exploring the project context to surface uncertainties, then engage in iterative two-question rounds with the user until all gaps are resolved before starting any implementation.

Frequently Asked Questions about clarify-first

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

FAQPage Schema
How do I clarify fuzzy project requirements before starting implementation?

The best way to prevent scope creep from unclear requirements is to systematically identify unknowns and force iterative clarifying questions across business logic, data, and external dependencies until all uncertainties are fully resolved before implementation.

How do you resolve information gaps and unknowns in project management workflows?

Resolving information gaps in project management involves grouping uncertainties by priority and conducting iterative questioning rounds, asking at most two questions per round until every point is addressed and a user-aligned plan is confirmed.

When do I need to ask clarifying questions before coding a feature with external dependencies?

You need to ask clarifying questions before coding when a feature involves fuzzy requirements, multiple viable implementation approaches, or external system dependencies where precise context is essential to prevent rework.

Does this requirements clarification approach work for projects with multiple viable approaches?

Yes, this approach works for projects with multiple viable approaches by surfacing unknowns through context exploration and running iterative two-question rounds to help users align on a single, confirmed decision before development proceeds.

What are the limitations of forcing iterative questioning for requirements gathering?

A limitation of forcing iterative questioning is that it strictly requires user confirmation before proceeding to implementation, meaning the workflow cannot advance or generate code until every surfaced uncertainty is explicitly addressed by the user.