confidence-aware-planning

Enforce honest confidence signaling and clarify before drafting plans.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill confidence-aware-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: confidence-aware-planning
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/confidence-aware-planning
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill confidence-aware-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Not every task comes with complete information. This skill enforces honest uncertainty signaling and adaptive planning when confidence is low.

Core Features & Use Cases

  • Confidence level definitions (HIGH, MEDIUM, LOW) with prescribed actions prior to planning.
  • Surface assumptions for MEDIUM confidence and require explicit risk/assumption documentation.
  • Stop-and-clarify workflow for LOW confidence: ask clarifying questions and do not draft a PLAN until answered.
  • Use cases include software planning, feature scoping, architecture reviews, and multi-agent coordination under uncertainty.

Quick Start

Before planning, assess your confidence level and, if it is LOW, ask clarifying questions first and do not draft a PLAN until answered.

Frequently Asked Questions about confidence-aware-planning

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

FAQPage Schema
How do I plan a software feature when project requirements are incomplete?

Planning with incomplete requirements requires assessing confidence levels first. This skill enforces honest uncertainty signaling by requiring explicit clarifying questions and assumption documentation before drafting any plans for ambiguous software features.

What is confidence-aware planning and how does it handle uncertainty?

Confidence-aware planning is a structured workflow that enforces honest confidence signaling. It defines HIGH, MEDIUM, and LOW confidence levels, surfaces assumptions for MEDIUM confidence, and blocks plan drafting for LOW confidence until clarifying questions are answered.

How do I document assumptions and risks when scoping ambiguous architecture reviews?

Document assumptions and risks by applying the MEDIUM confidence workflow during architecture reviews. This surfaces explicit assumptions and requires dedicated risk documentation before proceeding with the architectural planning process.

When should I ask clarifying questions instead of drafting a project plan?

Ask clarifying questions instead of drafting a plan when confidence is LOW. The stop-and-clarify workflow strictly prohibits producing any plan until explicit questions regarding ambiguous scope or incomplete information are answered.

Can I use structured confidence levels for multi-agent coordination under uncertainty?

Yes, structured confidence levels apply to multi-agent coordination under uncertainty. The defined HIGH, MEDIUM, and LOW confidence actions ensure all agents align on assumptions and require clarifications before proceeding with coordinated plans.

What are the limitations of confidence-aware planning for feature scoping?

The limitation of confidence-aware planning is that it strictly halts plan generation when confidence is LOW. If you cannot obtain answers to clarifying questions, the workflow will not produce a draft plan for your feature scoping task.