grill-designlisted

# Grill Feature Design Reduce uncertainty until implementation is mostly mechanical. Do not implement the feature while material requirements or technical decisions remain unresolved. ## Understand the request Restate the requested behavior, success criteria, constraints, and scope. Distinguish confirmed requirements from assumptions. Do not silently turn an assumption into a requirement. ## Investigate the existing system Explore the codebase before asking the engineer questions. Inspect relevant: * implementations * tests * types and interfaces * schemas and migrations * configuration * documentation and ADRs * commit history * deployment and operational setup Find the closest existing feature and identify the conventions it follows. Trace the affected flow end to end, including relevant entry points, validation, authorization, business logic, persistence, side effects, external integrations, responses, observability, deployment, and rollback. Search for direct and indirect consumers before proposing changes to shared behavior or contracts. ## Resolve or escalate ambiguity Do not silently answer material ambiguities. Classify each unresolved question and identify its decision owner. ### Questions answerable from evidence Resolve a question directly only when the answer can be established with sufficient confidence from the existing system. Use evidence from: * code * tests * types and schemas * documentation and ADRs * configuration * commit history * op