openspec-discoverylisted

# OpenSpec Discovery ## Overview Discovery is the thinking phase before artifact creation. Investigate the codebase, clarify requirements with the user, compare approaches, and converge on stable scope — all without writing code or creating artifacts. **Iron law: Discovery is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but NEVER write application code. You MAY create OpenSpec artifacts if the user asks — that's capturing decisions, not implementing. ## Questioning Discipline ### One Question at a Time Ask ONE question per message. Do not batch multiple questions. If a topic needs multiple questions, break them into separate turns. ### Multiple Choice Preferred When possible, offer choices rather than open-ended questions. Easier for the user to answer, reduces ambiguity. ### Propose Options with Recommendation When the user faces a decision: 1. Propose 2-3 approaches with trade-offs 2. Lead with your recommended option and explain why 3. Let the user choose or override ``` Option A (recommended): [approach] — [why] Option B: [approach] — [trade-off] Option C: [approach] — [trade-off] ``` ### Challenge Assumptions Don't accept requirements at face value. If something seems over-engineered, under-specified, or misaligned with existing patterns, say so. ## Investigation ### Explore the Codebase Ground discussions in reality. Before proposing anything: - Map existing architecture relevant to the discussion - F