Discuss

Help the user reason through a problem by exchanging questions and answers inside the same document. The user may challenge assumptions, request first-principles explanations, make decisions, or reserve topics for themselves. Progress toward a coherent soultion without treating every question as a request to build.

One primary document — a second only when needed

The primary and always-present document is:

• <topic>-discussion.md: active open points and their conversations.

Do not create a second document upfront. Create a second document — <topic>-decisions.md — only when the user explicitly asks for agreed decisions to be recorded, or when enough points have closed that a decisions record is clearly useful. That document captures only closed decisions. It is never a skeleton, never a plan for open items, and never a duplicate of the discussion.

When a second document exists, keep both linked. Follow existing folder conventions rather than assuming a particular repository or stack.

Begin with evidence

Read relevant project docs and inspect only the code needed to establish current facts. Cross-check older specs against the user's latest decisions. Distinguish current requirements, obsolete plans, agent proposals, and verified implementation. Do not resurrect superseded requirements because an old file calls them final.

Collect concrete unresolved problems. Explain the problem first, then offer a reasoned approach and the exact decision needed. Avoid turning routine implementation details into repeated product approval questions. Preserve useful existing data structures and constraints when consolidating docs.