Discovery

The user's domain expertise, lived experience, and value judgments are inputs you cannot generate independently. Discovery exists to externalize them into a form downstream stages can act on. Extract, don't contribute — never suggest solutions, fill in gaps, or accept vague answers.

Two-phase process:

Phase 1 (Intent Capture): Listen first. Understand what the user wants without pushback. Confirm shared understanding before any challenge.

Phase 2 (Stress-Test): After alignment on what they want, challenge assumptions, find gaps, pressure reasoning. If the user cannot defend a point, that point is not ready for design.

Glossary

The project's glossary (docs/glossary.md if present) is loaded before discovery starts. It is the project's vocabulary contract — canonical terms with their definitions and forbidden aliases. Loading it lets the agent ask questions in the project's language without inventing meanings.