plan-interrogate
Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.
Best for Design review sessionsWorks with GitHubLow risk
⌘source
- author
@rohitg00- language
- JavaScript
★1.9kstars
173forks
Apr 18, 2026
✦overview.md
Key Features
- ·Stress-tests plans before implementation
- ·Extracts and resolves decision trees
- ·Asks one focused question at a time
- ·Provides recommended answers with reasoning
- ·Checks existing codebase for answers
- ·Exits only when all decisions are resolved
Use Cases
- →Pressure-testing a software design before writing code
- →Walking through complex decision trees systematically
- →Resolving open decisions in dependency order
Best for
- ✓Design review sessions
- ✓Complex system planning
Not ideal for
- !Simple or already-decided plans
- !Rapid prototyping without thorough planning
FAQs
name
plan-interrogate
description
Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.
user-invocable:true
plan-interrogate
Drive a plan from sketch to commitment by resolving every open decision before any code is written.
Method
- Restate the plan in one paragraph. Confirm with the user that this is the plan being interrogated. Do not proceed on a mis-restatement.
- Extract the decision tree. Every branch point becomes a node. Mark
each node as open (undecided) or resolved. A resolved node
carries a source tag:
user(the user answered),inferred(the codebase or an existing constraint settled it). - Resolve in dependency order. A node is ready when every node it depends on is resolved.
- For each ready open node, ask exactly one question. Keep the question tight and binary or small-multiple-choice when possible.
- Pair every question with a recommended answer and one sentence of reasoning. The user can confirm, pick a different option, or push back.
- Before asking, check whether the answer already lives in the codebase,
prior commits, or an existing doc. If so, skip the question and mark
the node resolved with source
inferred: <path>. - Exit only when zero nodes are open. Print the resolved tree as a flat
$install
1-click copynpx skills add rohitg00/pro-workflow --skill plan-interrogateSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.