Menu
Plan differently when the agent has low certainty — ask for clarification or narrow scope instead of pretending full understanding.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Optimize token usage and context window discipline. Reduce costs and improve response quality through smart context management.
Unified context lifecycle for FlowDeck sessions — ingest, filter, prune, protect, summarize, and persist with telemetry.
Predict affected files, modules, APIs, tests, and DB paths before changes. Returns an impact map for human review.
Map architecture, conventions, and file structure into `.codebase/`. Use when onboarding or before deep feature work.
Protect critical context from pruning during compaction. Preserve active plans, safety files, pending operations, and user intent anchors.
Load full project context at session start. Read STATE.md, PLAN.md, PROJECT.md, CONVENTIONS.md, and ARCHITECTURE.md to brief any agent on where work stands.
| name | confidence-aware-planning |
| description | Plan differently when the agent has low certainty — ask for clarification or narrow scope instead of pretending full understanding. |
| origin | FlowDeck |
Not every task comes with complete information. This skill enforces honest uncertainty signaling and adaptive planning when confidence is low.
| Level | Meaning | Action |
|---|---|---|
| HIGH (≥80%) | Well-understood scope, clear precedent in codebase | Proceed to plan normally |
| MEDIUM (40–79%) | Partial understanding, some unknowns | Surface assumptions, narrow scope, flag for review |
| LOW (<40%) | Significant unknowns, no clear precedent | Ask clarifying questions first, do not plan until answered |
.codebase/ARCHITECTURE.mdBefore planning ANY task:
/fd-reviewWhen confidence is LOW, ask in this format:
Before I can plan this, I need to understand:
1. [Question about scope/behavior]
2. [Question about constraint or requirement]
3. [Question about existing system behavior]
I have LOW confidence because: [specific reason]
When confidence is MEDIUM, include at the top of every plan:
## Assumptions (MEDIUM confidence)
- A1: [assumption] — if wrong, [consequence]
- A2: [assumption] — if wrong, [consequence]
## Risks
1. [risk]: [mitigation]
Never write a plan that pretends HIGH confidence when the agent actually has LOW confidence. False certainty leads to wrong implementations and wasted effort.