clarify-loop

Clarify ambiguous requirements by generating batched questions with recommendations and structured logs.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill clarify-loop-zenbuapps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify-loop
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/clarify-loop
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill clarify-loop-zenbuapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

只要在需求看起來細節不足時,透過系統化的提問循環來確保用戶需求被充分澄清與紀錄。

Core Features & Use Cases

  • Batch-driven clarification: 以批次形式提出問題,附上推薦與理由,促使快速且一致的需求釐清。
  • Interaction discipline: 設定提問節奏與回答上限,保持對話高效且可追蹤。
  • Clarification logging: 自動產生澄清紀錄,便於後續需求驗收與設計對齊。
  • Use case scenarios: 適用於需求發掘、使用者故事撰寫、驗收標準界定等情境。

Quick Start

在新專案啟動時啟用此技能,透過分批提出問題並自動產生澄清紀錄以系統性收斂需求。

Frequently Asked Questions about clarify-loop

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

FAQPage Schema
How do I clarify ambiguous requirements into structured user stories?

Batch-driven clarification shapes ambiguous requirements into coherent sequential questions, providing recommended options with justifications to systematically refine user stories. It operates in configurable batch sizes to maintain interaction discipline.

How does batch processing work for requirements clarification?

Batch processing for requirements clarification groups questions into configurable batch sizes with enforced answer limits, keeping the interactive dialogue efficient and traceable. Each batch provides recommended options with justifications to guide consistent user responses.

How do I generate traceable acceptance criteria from user stories?

Generate traceable acceptance criteria by running an interactive clarification loop that automatically records all user answers into a structured clarifications log. This log provides a verifiable foundation for downstream planning tools and design alignment.

What is the best way to enforce interaction discipline during requirements gathering?

Enforce interaction discipline by setting a configurable batch size and answer limits within the clarification loop. This maintains a structured questioning rhythm and prevents unbounded conversational drift during requirements gathering.

Can I use batch-driven prompts for new project requirement discovery?

Yes, you can use batch-driven prompts for new project requirement discovery by enabling the interactive dialogue at project startup. It systematically converges requirements by presenting questions in batches with recommended options and justifications.

How do I produce a structured clarifications log for downstream planning?

Produce a structured clarifications log for downstream planning by recording all session-based clarifications and answers throughout the batch-driven dialogue. The resulting summary maps directly to downstream tools needing defined acceptance criteria and user stories.