grounded-recommendation

To get evidence-based recommendations, present your technical scenario and the skill will gather findings such as code paths and constraints, then deliver a recommendation with explicit uncertainty and guardrails for safe decision-making.

Grounded technical advice for architectural choices involves surfacing multiple valid approaches, analyzing their trade-offs and risks, and proposing an evidence-based path with explicit rationale and defined guardrails.

You need an evidence-based approach when multiple valid architectural approaches exist, trade-offs are involved, or outcomes depend heavily on actual code behavior and your specific environment constraints.

Analyze trade-offs by gathering findings on code paths and constraints first, presenting those findings, and then delivering a recommendation that explicitly states uncertainties and guardrails for each valid implementation approach.

Yes, this skill delivers recommendations with explicit uncertainty and guardrails by presenting findings on code behavior and constraints first, then proposing a grounded technical path with clearly defined safety limits.

The main limitation is that grounded recommendations depend entirely on gathering relevant findings about actual code behavior and environment constraints, meaning the resulting advice is bounded by available evidence and carries explicit uncertainty.