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.
git clone https://github.com/rohitg00/pro-workflow.git--- 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 1. Restate the plan in one paragraph. Confirm with the user that this is the plan being interrogated. Do not proceed on a mis-restatement. 2. 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). 3. Resolve in dependency order. A node is ready when every node it depends on is resolved. 4. For each ready open node, ask exactly one question. Keep the question tight and binary or small-multiple-choice when possible. 5. Pair every question with a **recommended answer** and one sentence of reasoning. The user can confirm, pick a different option, or push back. 6. 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>`. 7. Exit only when zero nodes are open. Print the resolved tree as a flat list: `Decision - Choice - Source (user | inferred: <path>)`. ## Anti-patterns - Asking multiple questions at once. The user loses context and you lose the ability to react to each answer individually. - Asking before exploring. If a fifteen-second read would answer the question, read first. - Asking without a recommendation. A question without a stance is a survey; it offloads design onto the user. - Rolling past an unresolved node. If a dependency is not pinned, the downstream question is premature. ## Outputs The interrogation produces three artifacts, not just answers. Offer to write each; do not force it. 1. **Decision ledger** (always). The resolved tree as a flat list: `Decision - Choice - Source (user | inferred: <path>)`. 2. **`CONTEXT.md`** (when the interrogation surfaced project-specific terms). A short shared-language file: every domain term you and the user had to pin down, with a one-line definition in the project's own words. This is what stops the agent from using twenty words where one will do next session, and keeps names in code consistent. One term per line: `term - what it means here`. Point future sessions at it. On re-run, merge new terms in place rather than overwriting existing ones. 3. **Decision records** (for contested or hard-to-reverse nodes only). One short record per decision that a future reader would question: the context, the choice, the alternatives rejected, and why. Keep them in `docs/decisions/NNNN-slug.md`. Read the directory first and number from the highest existing record so two records never collide. Skip the obvious ones - a record for a trivial choice is noise. ## Output contract The decision ledger the user can paste into the plan doc. No prose summary. No hedging. If the user declines to decide a node, mark it `DEFERRED` with the reason the user gave - this is not the same as open. When you write `CONTEXT.md` or a decision record, keep it in the project's language, not a generic template.
["Identify the plan you want to interrogate (e.g., a product launch, marketing campaign, or operational process).","Copy the prompt template into your AI tool and replace [PLAN_NAME] with your plan’s name.","Answer each question sequentially. The AI will surface hidden assumptions, risks, or gaps in logic.","If the AI identifies a critical flaw, pause the interrogation and revise the plan before proceeding.","Use the final output to document decision points, risks, and next steps for stakeholders."]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/rohitg00/pro-workflow/tree/main/skills/plan-interrogateCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Walk me through the decision tree for [PLAN_NAME]. Start at the first decision point and ask me one question at a time to stress-test the logic. After each answer, point out the next branch and the risks or assumptions it reveals. Stop when we reach a terminal node or when you’ve uncovered a critical flaw. Begin with: 'What is the first decision point in [PLAN_NAME]?'
Let’s interrogate the decision tree for *Project Phoenix*, a quarterly product launch plan. 1. **First decision point**: *Should we launch in Q3 or delay to Q4?* - You answer: *Q3.* - **Risk identified**: Q3 overlaps with a major competitor’s launch. Assumption: our marketing can outspend theirs by 20%. - **Next question**: *Do we have budget to match their ad spend in Q3?* 2. **Next branch**: *Budget confirmed?* - You answer: *No, only 10% increase.* - **Risk identified**: Competitor’s spend is 3x ours. Assumption: organic social growth will offset paid media gap. - **Next question**: *What’s the projected organic reach growth rate?* 3. **Next branch**: *Organic reach growth rate?* - You answer: *15% MoM.* - **Risk identified**: Competitor’s paid reach is 5x ours. Assumption: 15% MoM organic growth is sufficient to close the gap. - **Next question**: *Do we have contingency funding to increase paid spend by 50% if organic lags?* 4. **Next branch**: *Contingency funding?* - You answer: *No.* - **Critical flaw identified**: No fallback if organic growth underperforms. Recommendation: Delay launch to Q4 or secure emergency budget. **Result**: The plan fails its stress test at the *contingency funding* node. Recommend revising the Q3 timeline or allocating a reserve fund.
skills-collection
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan