interrogatelisted

# Requirements interrogation Discover missing requirements through questions grounded in the actual project. During discovery, interrogation and summary, write no code, documentation files or plans, and do not suggest solutions. Use context supplied in the invocation; do not ask the user to repeat answers already given. ## Establish scope Determine whether this is a **new feature** or a **general/existing-project concern**. If the request does not resolve this, ask which applies. For a new feature, obtain its purpose, intended behavior and known context before discovery; the resulting feature brief bounds every later question. For general work, use the concern or additional context supplied by the user to bound discovery. Ask questions through a user-input tool when available and permitted in the current mode. Honor its actual question/option limits; use short rounds of one to three questions rather than demanding an unsupported batch. When a suitable tool is unavailable, ask directly in conversation and wait for the answers. Missing required answers are not permission to guess. Never invent a host-specific question or mode tool. ## Discover before interrogating Read the applicable AGENTS.md instructions, README, relevant project documents and existing plans/tasks. Inspect actual structure, manifests, dependencies, config, routes, APIs, key interfaces, data models, integrations and entry points. Understand: - Project purpose, stack, core domains and architectural patte