plan-interrogate

Stress-tests implementation plans by resolving every open decision one question at a time.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill plan-interrogate-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-interrogate
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/plan-interrogate
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill plan-interrogate-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often contain hidden undecided branches that surface mid-implementation as costly rework. This Skill walks a plan's decision tree before any code is written, forcing every open decision to be resolved, inferred from the codebase, or explicitly deferred. ## Core Features & Use Cases - Decision Tree Extraction: Converts a plan into nodes marked open or resolved, with each resolved node tagged by source (user answer or inferred from the codebase). - One-Question-at-a-Time Interrogation: Asks a single tight question per ready node, always paired with a recommended answer and one sentence of reasoning. - Codebase-First Resolution: Checks the repository, prior commits, and existing docs before asking, marking answers as inferred with a source path. - Use Case: Before implementing a new caching layer, run the interrogation to pin down storage backend, TTL policy, and invalidation strategy, producing a decision ledger to paste into the plan doc. ## Quick Start Ask the AI to stress-test your implementation plan using plan-interrogate before writing any code.

Frequently Asked Questions about plan-interrogate

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

FAQPage Schema
How do I stress-test a design plan before implementation?

Restate the plan, extract its decision tree, and resolve each open node in dependency order by asking one question at a time. Each question comes with a recommended answer, and the process ends with a flat decision ledger you can paste into the plan doc.

What is a decision tree review for software plans?

It is a method that turns every branch point in a plan into a node marked open or resolved. Resolved nodes carry a source tag showing whether the user answered or the answer was inferred from the codebase or existing docs.

Does plan-interrogate check the codebase before asking questions?

Yes. Before asking any question, it checks whether the answer already exists in the codebase, prior commits, or existing documentation. If found, the node is marked resolved with source inferred and the file path.

What happens if I decline to decide a question during plan review?

The node is marked DEFERRED along with the reason you gave, which is distinct from leaving it open. The interrogation only exits when zero nodes remain open, so deferred nodes are explicitly recorded in the final ledger.

When should I not use one-question-at-a-time plan interrogation?

Avoid it for trivial plans with no real branch points, where a full decision tree adds overhead without value. It is designed for plans with multiple interdependent open decisions that would otherwise surface as rework during implementation.