interrogate-plan

Inspect codebases to identify gaps and assumptions in project plans.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/lhohan/agentfiles --skill interrogate-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interrogate-plan
Source: https://github.com/lhohan/agentfiles/tree/main/agents/dotagents/.agents/skills/interrogate-plan
Command: npx skills add https://github.com/lhohan/agentfiles --skill interrogate-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect the codebase to identify gaps and assumptions in a plan, then drive clarity through structured questioning until shared understanding is reached.

Core Features & Use Cases

  • Codebase-first planning: inspect artifacts to surface unknowns and risks.
  • Design-tree walkthrough: resolve design decisions and dependencies one-by-one.
  • One-question-at-a-time interaction: present recommended answers and guide user acceptance.

Quick Start

Begin by scanning the repository to surface unknowns, then ask one clarifying question at a time until all decisions are resolved.

Frequently Asked Questions about interrogate-plan

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

FAQPage Schema
How do I identify gaps and assumptions in a software project plan?

A design-tree approach resolves design decisions and dependencies one-by-one in software planning. It walks through each decision sequentially, presenting recommended answers and guiding user acceptance to ensure no re-confirmation of accepted decisions is needed.

How do I clarify project requirements using codebase inspection?

Yes, a one-question-at-a-time interaction presents recommended answers and guides user acceptance sequentially. This structured questioning drives clarity in software planning without overwhelming the user or re-confirming accepted decisions.

What is the best way to track decisions during software architecture planning?

Use interrogate-plan when your project plan requires iterative alignment of architecture, requirements, and dependencies. It is suited for scenarios where codebase inspection is needed to surface unknowns and drive clarity through structured questioning.

How does a design-tree walkthrough help with software planning decisions?

This approach is limited to software planning scenarios where architecture and dependencies require iterative alignment. It focuses on codebase-first inspection and structured questioning, and does not re-confirm accepted decisions once resolved.