Deep Deliberation

Outline problems, stakeholders, and root causes before proposing solutions.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/melissa-pereira-deel/creative-technologist-agent --skill deep-deliberation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Deep Deliberation
Source: https://github.com/melissa-pereira-deel/creative-technologist-agent/tree/main/skills/deep-deliberation
Command: npx skills add https://github.com/melissa-pereira-deel/creative-technologist-agent --skill deep-deliberation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In fast-moving teams, valuable work often stalls or backfires when people jump to solutions before fully understanding the problem. Deep Deliberation provides a structured approach to frame a problem, surface constraints, and align on root causes before designing or implementing a solution.

Core Features & Use Cases

  • Two Minds: a waking mind for problem framing and a background mind for creative synthesis, enabling deeper understanding before solutioning.
  • Problem Understanding over Solution Generation: ensures explicit problem statements, constraints, and knowledge gaps are identified before any approach.
  • Deliberation Guardrails: timers, explicit questions, and readiness checks to prevent rushed decisions on novel problems.
  • Practical Use Cases: design debates, architecture reviews, or any scenario where clarity is key to quality decisions.

Quick Start

Describe the problem clearly, list constraints, and identify what you don't know before proposing any solution.

Frequently Asked Questions about Deep Deliberation

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

FAQPage Schema
How do I stop my team from rushing to solutions before understanding the problem?

To stop teams from rushing to solutions, apply structured problem framing to outline exact problems, stakeholders, and root causes before moving to design or code. Deliberation guardrails like timers and readiness checks prevent premature implementation on novel problems.

What is structured problem framing in design and architecture reviews?

Structured problem framing in design and architecture reviews is a deliberation process that ensures explicit problem statements, constraints, and knowledge gaps are identified before proposing any approach. It uses dual-mind synthesis to align teams on root causes.

When do I need to use structured deliberation before implementation?

You need structured deliberation when teams argue about approaches or rush to implement without clarity during design debates or architecture reviews. It enforces readiness criteria and background mind synthesis before transitioning to design or code.

How do I identify root causes and constraints before proposing a solution?

To identify root causes and constraints before solutioning, describe the problem clearly, list constraints, and identify knowledge gaps. A background mind handles creative synthesis while a waking mind frames the problem to ensure deep understanding.

Does design thinking work with deliberation guardrails for novel problems?

Design thinking works effectively with deliberation guardrails by adding timers, explicit questions, and readiness checks to prevent rushed decisions. This combination ensures problem understanding takes priority over immediate solution generation.

What are the limitations of deliberation steps in fast-moving teams?

The limitation of deliberation steps in fast-moving teams is the required time investment for problem framing and dual-mind synthesis. Teams must pause to outline exact problems and satisfy readiness criteria, which delays immediate design or code implementation.