clarify

Filter non-critical clarification questions through a 4-stage funnel.

437|45|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill clarify-zaxbyhub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/clarify
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill clarify-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates unnecessary user interruptions during AI architect planning by filtering out non-critical clarification questions via a structured 4-stage funnel, ensuring users are only asked for decisions that genuinely require their input.

Core Features & Use Cases

  • 4-Stage Clarification Funnel: Systematically inventories all material uncertainties, classifies each item, consults the critic sounding board, and surfaces only required user decisions.
  • Critic Sounding Board Integration: Leverages critic review to drop unnecessary questions, rephrase unclear ones, and resolve items where safe defaults exist.
  • Always-Surface Category Enforcement: Guarantees critical decisions around scope, security, compatibility, and breaking changes are never silently dropped.
  • Use Case: For an ambiguous request to add a new payment processing feature, the architect runs this protocol to only ask the user about security risk tolerance and rollout strategy, rather than interrupting them with questions about internal implementation details that can be resolved from existing context.

Quick Start

Use the clarify skill to run the structured clarification funnel on the user's ambiguous request for a new user authentication system and return only the decisions that require user input.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I stop my AI architect from interrupting with unnecessary clarification questions during software planning?

To stop unnecessary AI architect interruptions, use a structured clarification funnel that filters non-critical questions, consults a critic sounding board to resolve safe defaults, and surfaces only genuine user decisions regarding scope, security, and compatibility.

What is a gated clarification workflow for ambiguous software development requests?

A gated clarification workflow is a multi-stage filtering process that inventories material uncertainties, applies critic review to drop unnecessary questions, and enforces always-surface categories for critical decisions before interrupting the user.

How do I classify material uncertainty in software requirements to reduce user interruptions?

You classify material uncertainty by running ambiguous requests through a 4-stage funnel, separating internal implementation details that can be resolved from context from critical scope, security, and breaking change decisions that require user input.

Does the clarify protocol enforce surfacing of security and compatibility decisions?

Yes, the clarify protocol enforces always-surface category guarantees, ensuring critical decisions around security risks, compatibility, breaking changes, and rollout strategy are never silently dropped by the critic sounding board.

When should I use a critic sounding board for AI planning clarification?

Use a critic sounding board for AI planning when you have ambiguous requests requiring material uncertainty classification, allowing the critic to drop unnecessary questions, rephrase unclear ones, and resolve items where safe defaults exist.

Can I apply a clarification funnel to ambiguous feature requests like adding payment processing?

Yes, you can apply a clarification funnel to ambiguous feature requests to isolate genuine user decisions, such as security risk tolerance and rollout strategy for payment processing, while resolving internal implementation details automatically.