lev-cdo

name	lev-cdo
description	[WHAT] Graph-based thinking playbook (CDO) [HOW] Classifies input by complexity, routes to appropriate workflow (Quick/Base/Deep/Epic) [WHEN] Use for design, architecture, and complex problem decomposition requiring multi-perspective analysis [WHY] Provides a repeatable thinking playbook instead of ad-hoc brainstorming. Triggers: "think", "design", "architect", "complexity", "cdo", "graph", "multi-agent", "deep analysis"
skill_type	playbook
category	process-thinking
lifecycle_integration	{"stage":"crystallizing","input_artifact":"report.md","output_artifact":"proposal.md"}
related_skills	["skill://lev-research","skill://lev-find","skill://planning","skill://work","skill://lev-ultra"]
protocol_handlers	["lev://cdo?complexity={quick|base|deep|epic}","lev://debug?mode=rca"]
plankton	false

lev-cdo - Graph-Based Agentic Thinking

Lev Concept

What is this? CDO (Complexity-Driven Orchestration) is a graph-based execution system where agents read/write to disk in structured workflows. Problems are classified by complexity, then routed to appropriate patterns (Quick/Base/Deep/Epic).

Why does it exist? Traditional linear thinking fails for interconnected problems. CDO prevents groupthink by ensuring agents never see each other's work during execution - only the final synthesis step reads all artifacts together.

When to use it:

• Design work - Architecture decisions, system design
• Complex debugging - Root cause analysis with multiple hypotheses
• Strategic analysis - Multi-perspective evaluation of decisions
• Assumption exploration - Socratic questioning of beliefs
• Research synthesis - Integrating findings from multiple sources

When NOT to use it:

• Simple questions with known answers → Use Quick workflow or just answer
• Single perspective sufficient → Direct execution
• No complexity/interdependencies → Standard task execution

---

CLI Commands

Primary Commands

# Auto-classify and route to appropriate workflow
lev cdo "{query or problem statement}"

# Force specific complexity level
lev cdo --complexity=quick "{query}"
lev cdo --complexity=base "{query}"
lev cdo --complexity=deep "{query}"
lev cdo --complexity=epic --bd-epic=clawd-xxx "{query}"

# Classification only (no execution)
lev cdo classify "{input}"

# Debug mode (RCA workflow)
lev cdo debug "{error description}"

Examples

# Example 1: Auto-classify (likely: base)
lev cdo "Should we use GraphQL or REST for the API?"

# Example 2: Force deep complexity
lev cdo --complexity=deep "Explore assumptions behind microservices"

# Example 3: Debug workflow
lev cdo debug 


lev cdo --complexity=epic --bd-epic=clawd-042