Results for “clarification-questions”

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

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.

Refines task understanding through iterative questioning before executing, using the Joyride extension for human input.

Provides a structured methodology for solving nontrivial, ambiguous problems by framing outcomes, selecting evidence, routing specialists, choosing options, and verifying results.

Guides users to uncover the real question behind surface problems, reframe decisions, and challenge assumptions through structured questioning.

Create detailed phase plan (PLAN.md) with verification loop

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

Analyze draft prompts to identify intent, scope, and missing context, then generate an optimized prompt with ECC component recommendations. Advisory only — never executes the task.