deep-probe

Guide iterative design questioning to converge on shared decisions.

12|2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/haomingz/kimi-skills --skill deep-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-probe
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/deep-probe
Command: npx skills add https://github.com/haomingz/kimi-skills --skill deep-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sequentially interrogate every detail of a proposed plan or design, guiding both parties to reach clear consensus by drilling down through each decision branch.

Core Features & Use Cases

  • Step-by-step interrogation of each design branch to surface dependencies and assumptions.
  • Provide each prompt with a suggested answer and rationale to accelerate alignment.
  • If a question can be answered by reading code or references, consult them directly and cite findings.

Quick Start

Initiate the first decision branch and start the one-question-at-a-time review until consensus is reached.

Frequently Asked Questions about deep-probe

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

FAQPage Schema
How do I guide a design review session to reach consensus on branching decisions?

Guide a design review to consensus by using step-by-step interrogation of each design branch. This process surfaces dependencies and assumptions, asking one question at a time until all parties align on a shared outcome.

What is the best way to systematically question design assumptions during architecture planning?

Systematically question design assumptions during architecture planning by sequentially interrogating every detail of the proposed plan. This method drills down through each decision branch to surface hidden dependencies and validate choices.

Can I use code references to validate design decisions during a critical-thinking review?

Yes, you can use code references to validate design decisions during a critical-thinking review. If a question can be answered by reading code or documentation, the process consults them directly and cites findings.

Does this step-by-step questioning approach work for strategic decision-tree sessions?

Yes, this step-by-step questioning approach works for strategic decision-tree sessions. It is specifically applicable to strategic sessions where branching decisions must be validated and aligned through one-question-at-a-time interaction.

When should I not use one-question-at-a-time design probing?

You should not use one-question-at-a-time design probing when rapid, high-level feedback is needed without validating specific branching decisions. It is designed for detailed interrogation where drilling down into assumptions is required.