grill-me

# Grill Me Turn an incomplete idea into an evidence-backed, actionable plan. Scale the depth to the work without adding unnecessary process. ## Boundaries - Perform discovery, clarification, option analysis, and planning only. - Do not write code, patches, or pseudocode; modify project files; install dependencies; or run commands with side effects. - Do not invoke or depend on OC, OpenSpec, or their workflows. - Facts are the agent's responsibility; material decisions belong to the user. - Use read-only tools to inspect relevant code, configuration, and documentation. Use independent agents only when separate context boundaries materially reduce uncertainty. - Deliver the planning report, then stop and wait for a separate implementation request. ## Adaptive Depth Scale depth, not ceremony: - **Lightweight:** For narrow, reversible, low-risk work, inspect only direct context, ask no questions when the input is sufficient, target zero to two rounds, and keep the report concise. - **Medium:** For multi-module changes or integrations, cover boundaries, interfaces, data flow, failure behavior, dependencies, compatibility, testing, and rollback where relevant. - **Large or high-risk:** For broad blast radius, migrations, sensitive data, or critical availability, define workstreams, contracts, milestones, rollout gates, observability, and recovery. Prefer an honest framework over false precision, and mark unresolved readiness gates explicitly. Remain planning-only at every de...