Resolve ambiguous user requests into a concise Context Brief via Q&A and codebase exploration.
npx skills add https://github.com/2lab-ai/oh-my-claude --skill clarify-2lab-ai
Please help me install this Agent Skill. Skill: clarify Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/clarify Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill clarify-2lab-ai
Converts ambiguous or underspecified user requests into a clear, verifiable Context Brief so teams can proceed with implementation without repeated clarification cycles.
Ask the assistant to run stv:clarify on your vague task description to interview for missing details and explore the codebase, then present a Context Brief.
High-intent search queries and answers about installing and using this skill.
You can resolve ambiguous requests by running an iterative one-question Q&A alongside automated codebase exploration to produce a concise Context Brief covering goals, scope, constraints, and success criteria.
Gathering technical context for unclear tickets involves launching codebase exploration subagents to report related files, patterns, and constraints while simultaneously interviewing the user to surface technical risks and assumptions.
Automated codebase exploration during early scoping works by integrating subagents that scan the codebase to report related files, patterns, and technical constraints, feeding the results directly into a comprehensive Context Brief.
Yes, you can assess implementation complexity while resolving ambiguities by synthesizing user answers and codebase context into a Context Brief that includes a dedicated complexity assessment for routing.
A context brief for software engineering tasks should include the goal, in and out-of-scope items, technical context, constraints, success criteria, open questions, and a complexity assessment to serve as a single source of truth for implementation.
Use a clarification process for software requirements during early scoping, when handling unclear tickets, or receiving feature requests that lack technical assumptions and acceptance criteria to prevent repeated clarification cycles.
nbarthelemyConduct project specification interviews and generate a complete SPEC.md.
Aiden-KwakAnalyze project structure and tech stack to generate detailed requirement documents.
DergaczAutomate implementation and verification of technical plans from plan.md files.
tmdgusyaResolve vague requests through iterative Q&A and parallel codebase exploration.
