Grounded

Overview

Use this skill to slow down architecture advice until the relevant system shape is source-derived. The goal is not impossible certainty; the goal is to avoid confident recommendations that are not anchored in files, call sites, tests, configuration, and observed project boundaries.

Grounding Workflow

1. Define the recommendation scope in one or two sentences. Include the specific user decision being supported and the architectural surfaces likely affected.

2. Build a reading map before recommending. Identify likely entry points, core modules, adapters, schemas, tests, configs, docs, and call sites. Use fast repository search first, then read the files that establish ownership and behavior.