consult

Trigger structured consultation when implementation obstacles require tradeoff alignment.

26|3|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill consult-davidlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consult
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/consult
Command: npx skills add https://github.com/davidlee/spec-driver --skill consult-davidlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents silent drift when unanticipated obstacles, tradeoffs, or emergent complexity would cause impactful architectural or agent-driven decisions to be made without alignment.

Core Features & Use Cases

  • Obstacle escalation with clear context: Forces a pause and a structured explanation of what changed and why it matters.
  • Decision and tradeoff alignment: Surfaces multiple options and their tradeoffs before committing to adaptations that could alter planned functionality.
  • Guardrails for risky moves: Triggers consultation when new coupling/imports, substantial debugging/research, or policy/“heresy”-like ambiguity is at risk.
  • Use Case: During implementation, an agent proposes adding a new import/module that would change coupling and introduce ambiguity; this skill guides you to stop, summarize the findings, and request guidance before proceeding.

Quick Start

If you hit an unexpected blocker, tell the AI to stop, summarize the current context and discoveries, list the options and tradeoffs, and ask for guidance before continuing.

Frequently Asked Questions about consult

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

FAQPage Schema
How do I prevent architectural drift when implementation blockers change the plan?

To prevent architectural drift, you must stop and trigger structured consultation when unanticipated obstacles emerge. This forces a pause to summarize findings, present tradeoffs, and request guidance before proceeding with risky adaptations.

What is the best way to handle scope control during implementation tradeoffs?

Scope control during implementation tradeoffs requires surfacing multiple options and their impacts before committing. This ensures decisions that alter planned functionality are explicitly aligned rather than silently diverting the scope.

When do I need to trigger decision alignment for agent governance?

Decision alignment for agent governance is needed when an agent proposes adding new coupling, substantial debugging, or policy ambiguity. It acts as a guardrail to prevent unsafe, agent-driven decisions without explicit contextual summarization.

How do I escalate risk when an agent proposes unsafe architectural changes?

Risk escalation for unsafe architectural changes requires halting the task, summarizing the current plan and discoveries, listing options with tradeoffs, and asking a guidance-seeking question before proceeding.

Does scope control work without structured consultation when debugging diverts scope?

No, when research or debugging threatens to divert scope, structured consultation is required. It enforces a stop condition to contextualize the obstacle and align on the tradeoff before allowing the implementation to adapt.

What are the limitations of relying on stop conditions for decision alignment?

Stop conditions for decision alignment only trigger consultation; they do not resolve the obstacle. You must still manually summarize context, present explicit tradeoffs, and formulate a guidance-seeking question to proceed safely.