collaborative-judgment

Surface structured judgment calls with options and escalation rules during design and code review.

176|13|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/techygarg/lattice --skill collaborative-judgment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collaborative-judgment
Source: https://github.com/techygarg/lattice/tree/main/plugins/lattice/skills/collaborative-judgment
Command: npx skills add https://github.com/techygarg/lattice --skill collaborative-judgment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity and missing or conflicting knowledge during code generation, design, and review lead to silent decisions and hallucinations. This description ensures AI surfaces grounded judgment calls with structured options and explicit clarification when needed.

Core Features & Use Cases

  • Surface decision points only when grounded evidence supports multiple viable approaches.
  • Present 2-3 options with pros and cons and escalation rules for unresolved tradeoffs.
  • Provide a clear workflow for deciding, clarifying, and recording context anchors during design and code review.

Quick Start

Activate collaborative-judgment during ambiguous design or code decisions to surface grounded options and request targeted clarifications.

Frequently Asked Questions about collaborative-judgment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI from making silent assumptions during code generation?

To stop silent assumptions during code generation, surface judgment calls as structured options with explicit rationale. This forces the AI to present viable approaches and request targeted clarifications instead of guessing.

What is the best way to handle ambiguous design decisions in AI-assisted development?

Handling ambiguous design decisions requires surfacing grounded options with pros and cons. A two-option decision format with escalation rules ensures unresolved tradeoffs are explicitly clarified rather than silently resolved.

Can I use structured decision-making for conflicting information in design review?

You can use structured decision-making for design review to handle conflicting information. It exposes judgment calls, presents 2-3 options with pros and cons, and applies escalation rules for unresolved context anchors.

Why does AI hallucinate when facing missing information during code generation?

AI hallucinates with missing information because it makes silent decisions to fill gaps. Structured judgment calls prevent this by exposing ambiguity, requesting targeted clarifications, and forcing explicit two-option decisions.

When should I escalate unresolved tradeoffs in collaborative code design?

You should escalate unresolved tradeoffs in collaborative code design when grounded evidence supports multiple viable approaches but clarification is needed. Escalation rules trigger to request targeted user input for missing context anchors.