clarify

Delegate specification elicitation to a sub-agent and summarize final requirements.

9|Updated Aug 20, 2018
One-click install
npx skills add https://github.com/berlysia/dotfiles --skill clarify-berlysia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/berlysia/dotfiles/tree/main/.skills/clarify
Command: npx skills add https://github.com/berlysia/dotfiles --skill clarify-berlysia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clarify requires a sub-agent to iteratively elicit and document precise specifications from ambiguous user plans, while preserving the main context for continuity.

Core Features & Use Cases

  • Delegates specification clarification to a sub-agent and enforces a structured questioning flow.
  • Reads methodology guidelines (references/methodology.md) and iterates until all ambiguities are resolved.
  • Produces a concise final specification and presents next-step options to the user.

Quick Start

Provide your current plan or task and let Clarify iteratively generate a concise, complete specification.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I clarify ambiguous project requirements into precise specifications?▼

This tool clarifies ambiguous project requirements into precise specifications by delegating iterative questioning to a sub-agent, resolving all plan ambiguities while preserving the main context for continuity.

What is the best way to elicit detailed software requirements from a rough plan?▼

The best way to elicit detailed software requirements from a rough plan involves a structured workflow with a fixed round of iterative questions, reading methodology guidelines, and summarizing a final, testable specification.

How does context protection work during requirements clarification?▼

Context protection during requirements clarification works by delegating specification elicitation to a sub-agent, isolating iterative questioning to prevent context bloat in the main workflow.

Can I enforce a fixed number of questions when gathering project specifications?▼

Yes, you can enforce a fixed round of questions when gathering project specifications to systematically resolve all ambiguities before producing the final concise specification document.

Does requirements clarification work without external API dependencies?▼

Yes, requirements clarification works without external API dependencies, relying entirely on internal sub-agent delegation and methodology guidelines to drive the specification elicitation workflow.

When should I not use an iterative sub-agent for specification elicitation?▼

You should not use an iterative sub-agent for specification elicitation if your plan is already highly detailed and testable, as the fixed questioning workflow is specifically designed to resolve ambiguity.