interrogate

Stress-tests plans, designs, and specifications through disciplined one-at-a-time questioning.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill interrogate-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/interrogate
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill interrogate-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans, designs, and specifications often contain hidden assumptions, unresolved dependencies, and unexamined decision branches that surface only after costly implementation begins. This Skill systematically stress-tests your approach through relentless, structured questioning before you commit. ## Core Features & Use Cases - Decision Tree Walkthrough: Walks down each branch of your decision tree, resolving dependencies between decisions one by one. - One Question at a Time: Asks focused questions sequentially, always providing a recommended answer for each. - Codebase-Grounded Inquiry: Explores the codebase directly to answer questions when the answer exists in the code rather than asking you unnecessarily. - Use Case: Before starting a major refactor, invoke this Skill to have every aspect of your migration plan challenged until you reach a shared, validated understanding. ## Quick Start Ask the assistant to interrogate you relentlessly about your plan or design until every decision is resolved and understood.

Frequently Asked Questions about interrogate

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

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

Invoke this Skill with your plan, design, or spec and it will interrogate you one question at a time, walking each branch of the decision tree. Each question comes with a recommended answer so you can confirm or challenge it quickly.

How does the interrogation process work step by step?▼

The Skill asks questions one at a time rather than in a batch, resolving dependencies between decisions sequentially. When a question can be answered by exploring the codebase, it investigates the code directly instead of asking you.

When should I use plan interrogation instead of writing a spec directly?▼

Use it when you have a draft plan, design, or approach that needs validation before execution. It is best suited for stress-testing existing thinking, not for generating a specification from scratch.

Does the questioning use information from my codebase?▼

Yes. If a question can be answered by exploring the codebase, the Skill examines the code itself rather than asking you, keeping the interrogation grounded in the actual implementation.

What are the limitations of question-based plan validation?▼

It depends on the quality of the plan you bring and your engagement with each question. It does not execute or prototype the plan, so technical feasibility risks may still require testing or proof-of-concept work.