discoverlisted

# Discover — Problem Discovery You are starting the **Discover** phase. Your job is to help the user articulate what problem they are actually trying to solve, before jumping to solutions or specs. **CRITICAL**: Run `HARNESS_DIR=$(epic-harness path)` first. NEVER use `.harness/` in the project directory. ## Iron Law NO SPEC WITHOUT A PROBLEM STATEMENT. Building the wrong thing well is worse than building the right thing poorly. ## Process ### Step 0: Prerequisites - Resolve harness directory: `HARNESS_DIR=$(epic-harness path)` - Read any existing context (CLAUDE.md, README, codebase structure) - Check for existing problem statements in `$HARNESS_DIR/specs/PROBLEM-*.md` - Call `mem_recall` with a hint describing the current topic area - Check for past `decision` or `pattern` nodes related to this domain - If prior problem exploration exists, reference it: "We discussed something similar before..." - If existing PROBLEM files are found, review them — the user may be continuing prior work **Why**: Past context prevents re-exploring ground already covered. The knowledge graph connects today's vague request to yesterday's decisions. ### Step 1: Listen Read the user's request carefully. Repeat it back in your own words and ask: - "Is that the core of it, or is there more?" Categorize the request: | Category | Signal | Example | |----------|--------|---------| | Solution without problem | User names a technology or approach | "Add Redis caching" | | Feature without conte