Commands

Deep Planning

Investigate → discuss → plan → implement

Deep Planning follows a strict four-step process: silent investigation of your vault, targeted clarifying questions, comprehensive plan creation, and trackable task breakdown. No rushing to answers.

How it works

Four disciplined steps from
question to implementation plan

No rushing to answers. Deep Planning investigates your vault silently, asks the right questions, creates a comprehensive plan, then breaks it into trackable tasks with acceptance criteria.

1. Silent Investigation

Explore the vault for relevant documents, patterns, and prior art. No output yet — just deep research. The AI reads everything before saying anything.

Scanning 47 vault documents... found 12 relevant to this question

2. Targeted Discussion

Ask specific clarifying questions about requirements, constraints, and approach. Not generic questions — pointed ones that reveal the real constraints.

Is the 6-week deadline firm, or is quality the priority?

3. Comprehensive Plan

Generate a full plan with objectives, approach, task breakdown, dependencies, risks, and success criteria. Informed by investigation and discussion.

Plan: 4 phases, 23 tasks, 3 dependencies, 2 risks with mitigations

4. Task Checklist

Create trackable implementation steps with clear acceptance criteria for each. Not vague tasks — specific, testable, assignable work items.

☐ API endpoint returns 200 with valid JWT (est: 2h, depends: auth setup)

Think before you build

Not "let me start coding."
The best builders investigate before they execute.

Jump In
Start building immediately
Discover requirements mid-implementation
Rework when assumptions were wrong
No clear acceptance criteria
Ask QP
Silent investigation reads all relevant vault docs first
Targeted questions surface hidden requirements and constraints
Comprehensive plan with dependencies, risks, and success criteria
Every task has acceptance criteria you can test

Any complex initiative

Plan first. Build with confidence.

Anything worth building is worth planning properly.

Software Projects

Feature development, migrations, refactors, integrations

Research Initiatives

Literature reviews, experiment design, grant proposals

Business Launches

Product launches, market entry, partnership programs

Content Series

Book outlines, article series, course curricula

Legal Cases

Case strategy, discovery plans, motion timelines, deposition prep

Team Initiatives

Hiring plans, onboarding programs, process redesigns, culture projects

Ready to plan?

Open a Space in the Workspace and run /deep-planning from the Conductor.

Get AskQP