Results for “clarification-questions”

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Gera até cinco perguntas dirigidas para resolver pontos ambíguos do requirements e integra as respostas no documento. Use quando o usuário digitar "/reversa-clarify", "reversa-clarify", "esclarecer dúvidas" ou pedir para tirar pontos abertos do requirements antes de planejar. Etapa opcional do ciclo forward, entre `/reversa-requirements` e `/reversa-plan`.

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

Proceed through ordinary ambiguity by making reasonable assumptions, keeping momentum, validating as you go, and ending with a clear recap of decisions, changes, verification, and residual risk.

Clarifies ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "grill me", ask hard questions, request relentless interrogation, pressure-test assumptions, clarify scope/requirements, define success criteria, or request system-design/optimization decisions.

对 wiki 提问，综合检索相关页面后回答，好的回答可 crystallize 回 wiki

Deliberative consultation with Codex CLI. Ask, evaluate, critique, iterate until workable agreement.

Explain any concept in plain words with one concrete analogy - clear enough for a smart child or a busy outsider, never condescending, never wrong.

Deliberative consultation with Gemini CLI. Ask, evaluate, critique, iterate until workable agreement.

Write FAQ pages with comprehensive answers. TRIGGERS - Use when user needs help with faq-writer related tasks.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Find a unifying insight that eliminates multiple components, collapsing complexity by abstracting common patterns.

Use when content is verbose, repetitive, or padded and needs tightening while preserving meaning

Write FAQ pages with comprehensive answers. TRIGGERS - Use when user needs help with faq-writer related tasks.

Verify code changes work by running them. Proves through execution, not just inspection.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.

补充上下文，用更简单、明确的中文重新解释。

Verify that a change really works before you claim completion

Runs an interactive QA session, clarifying user-reported problems, exploring the codebase for context, and filing durable, user-focused GitHub issues.

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

Stores verified cross-session facts, decisions, preferences, and open questions without secrets, speculation, or monitoring.