consult

Determines safest next step from incomplete project information and unclear requirements.

Updated Aug 27, 2026

Search Tags:#planning #execution #recommendation #decision-making #risk #consult #repo-truth

Ready to run

npx skills add https://github.com/scripness/skills --skill consult-scripness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consult
Source: https://github.com/scripness/skills/tree/main/src/consult
Command: npx skills add https://github.com/scripness/skills --skill consult-scripness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify the safest next move in a project when the best action is not yet clear enough to execute or plan.

Core Features & Use Cases

Frames decision boundaries and differentiates between execute, plan, or consult for repo-truth driven tasks.
Provides evidence-based option comparisons, risk assessment, and durable plan carry-forward when needed.
Delivers a concise, actionable recommendation to move work forward safely.

Quick Start

Ask the user for AGENTS.md, specs, and current diffs, then compare options and report the safest next move.

Frequently Asked Questions about consult

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

FAQPage Schema

How do I choose the safest next move when my project direction is ambiguous?▼

To choose the safest next move, you need an evidence-based recommendation that grounds decisions in repo truth like AGENTS.md and specs, comparing options and assessing risks to clarify a bounded next step.

When should I consult project specs instead of immediately executing or planning?▼

You should consult project specs when the best action is not yet clear enough to execute or plan, requiring a bounded next step that frames decision boundaries and differentiates between execution, planning, or further consultation.

How do I make a decision-making comparison for risky repo changes?▼

Decision-making comparison for repo changes requires evaluating evidence-based options against repo truth like AGENTS.md and current diffs, assessing risks, and delivering an actionable recommendation to move work forward safely.

What is the best way to carry forward a durable plan after clarifying a recommendation?▼

The best way to carry forward a durable plan is to generate a copy-ready plan carry-forward from the evidence-based recommendation, ensuring the bounded next step satisfies requirements grounded in repo truth and specs.

Does this approach work for assessing risk in software engineering planning?▼

Yes, this approach works for assessing risk in software engineering planning by grounding decisions in repo truth, providing evidence-based option comparisons, and framing decision boundaries to ensure safe execution.

What limitations exist when consulting repo truth for ambiguous planning decisions?▼

A limitation when consulting repo truth is that it requires AGENTS.md, specs, and current diffs to be available; without these inputs, the evidence-based recommendation cannot accurately frame decision boundaries or assess risks.