interview

Drill down plan decisions and dependencies through guided branching questions.

20|6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/adrielp/ai-engineering-harness --skill interview-adrielp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/adrielp/ai-engineering-harness/tree/main/gemini/skills/interview
Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill interview-adrielp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview and stress-test plans or designs by relentlessly questioning until a shared understanding is reached, surfacing gaps and assumptions.

Core Features & Use Cases

  • Branching interview flow: Walks down each branch of the decision tree, explaining rationale and tracking decisions.
  • Dependency resolution: Identifies and resolves dependencies between decisions, requirements, and risks.
  • Use Case: When validating a plan before implementation, use this skill to drill into assumptions, gather clarifications, and align stakeholders.

Quick Start

Ask targeted, branching questions to validate my plan and surface hidden dependencies.

Frequently Asked Questions about interview

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

FAQPage Schema
How do I validate project assumptions and surface hidden dependencies before implementation?

To validate project assumptions, you can use structured branching questions that drill down into your plan's decision tree, tracking dependencies and surfacing gaps to reach a shared understanding with stakeholders.

What is the best way to stress-test a design plan with stakeholders?

Stress-testing a design plan requires guided, branching interviews that challenge decisions and dependencies, ensuring stakeholders clarify rationale and track next steps to uncover hidden risks.

How do I use a decision tree to identify risks and gaps in project planning?

Using a decision tree to identify risks involves applying branching interview flows that drill into each decision node, tracking dependencies between requirements to expose gaps and validate assumptions.

Can I resolve dependencies between project requirements through guided questioning?

Yes, you can resolve dependencies between project requirements by applying a structured interview flow that identifies and tracks connections between decisions, requirements, and risks across the plan.

Does plan validation work for both design scopes and broader project management?

Plan validation works across both design and project scopes, applying guided questioning to challenge decisions and dependencies regardless of the specific planning context.

When should I avoid using a branching interview flow for project validation?

You should avoid using a branching interview flow when your plan lacks complex decision trees or interdependent requirements, as simple plans may not require relentless questioning to surface gaps.