agentic-clarification

Resolve vague requests through iterative clarification and parallel codebase exploration.

3|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/alphabeen/oh-my-jinho --skill agentic-clarification-alphabeen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-clarification
Source: https://github.com/alphabeen/oh-my-jinho/tree/main/skills/agentic-clarification
Command: npx skills add https://github.com/alphabeen/oh-my-jinho --skill agentic-clarification-alphabeen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses vagueness in user requests by initiating an iterative clarification loop and coordinating parallel codebase exploration with subagents, producing a precise, actionable context brief.

Core Features & Use Cases

  • Iterative Q&A with one-question-per-message discipline to progressively narrow scope.
  • Parallel codebase exploration via subagents to surface architectural context and constraints.
  • Generates a structured Context Brief that informs downstream planning and reduces rework.

Quick Start

Begin by posing one clarifying question and launching a subagent to inspect the relevant project, then iterate until the context is clear and a brief can be produced.

Frequently Asked Questions about agentic-clarification

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

FAQPage Schema
How do I clarify vague software requirements before starting a refactor?

To clarify vague software requirements, you can use an iterative clarification loop that progressively narrows scope through targeted questions. This resolves ambiguity by producing a precise context brief for downstream planning workflows.

What is iterative clarification for resolving ambiguity in feature requests?

Iterative clarification is a process of resolving ambiguity in feature requests by asking one question per message. It progressively narrows the scope of underspecified requests to arrive at a precise actionable plan.

How do I generate a context brief for complex software projects with underspecified requirements?

You generate a context brief by guiding an iterative Q&A loop alongside parallel codebase exploration. This surfaces architectural constraints and produces a well-scoped brief for downstream handoff.

Does iterative clarification work for scoping data pipelines and feature ideas?

Yes, iterative clarification works for scoping data pipelines, feature ideas, and refactors. It is specifically designed for complex software projects where requirements are underspecified and multiple directions are plausible.

What is the best way to explore a codebase when planning a feature with vague requirements?

The best way to explore a codebase with vague requirements is coordinating parallel subagent exploration during an iterative Q&A loop. This surfaces architectural context and constraints to inform a structured context brief.