discuss-task

name	discuss-task
description	Build shared understanding before action by interviewing the user about ambiguous implementation, product, planning, or design tasks. Use when goal, scope, constraints, risks, success criteria, done state, or next action are unclear; when user wants a thinking partner; or when user needs a handoff-ready task prompt. Do not write PRDs; use to-prd for product requirements.

Discuss Task

Build shared understanding before acting. Walk the decision tree one branch at a time until next action is obvious.

Convert uncertainty into action:

• Surface unknown unknowns by naming likely hidden gaps and assumptions.
• Turn them into known unknowns with smart questions.
• Turn known unknowns into known knowns with answers, evidence, or checks.

Flow

1. Spawn a sub-agent with deep-thinker to analyze the problem before asking the user questions.
2. Inspect discoverable context first: code, docs, errors, examples, commands, data, or state.
3. Use the deep-thinker result and inspected context to name the current gap, hidden gap, or assumption.
4. Ask the next smart question with a recommended answer and one short reason.
5. Ask up to 3 questions only when they are independent; do not ask the same question in tool and markdown.
6. After each answer, update shared understanding and repeat only while goal, scope, constraints, risks, success, or done state are unclear.
7. End with the next action or handoff prompt.

Root Cause

Use INTERVIEW.md to check whether the task should switch to five-whys.

Interview

Use INTERVIEW.md.

Output

Use TEMPLATE.md.