interview-me

Guide users through branch-by-branch interviews to surface goals, constraints, and dependencies.

47|5|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/zvadaadam/az-skills --skill interview-me-zvadaadam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/zvadaadam/az-skills/tree/main/skills/productivity/interview-me
Command: npx skills add https://github.com/zvadaadam/az-skills --skill interview-me-zvadaadam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users to reach a shared understanding of a plan or idea by conducting a thorough, branch-by-branch interview that surfaces goals, constraints, and dependencies.

Core Features & Use Cases

  • Branch-by-branch questioning to surface assumptions, risks, and trade-offs
  • Dependency mapping and context consolidation to produce a concrete plan
  • Use Case: when starting a new feature or project, to clarify scope and responsibilities before design

Quick Start

Describe your plan and I will start an in-depth interview to illuminate all decisions and dependencies.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I align project goals and dependencies before starting feature design?

To align project goals before feature design, conduct a structured branch-by-branch interview to surface constraints, map dependencies, and consolidate context into a shared plan with documented decisions and trade-offs.

What is the best way to surface hidden risks and assumptions during project planning?

The best way to surface hidden risks during project planning is using a decision-tree interview format that probes branch-by-branch, forcing you to articulate assumptions and constraints before finalizing the plan.

Can I use an interview-based approach to clarify project scope and responsibilities?

Yes, you can use an interview-based approach to clarify project scope by working through targeted questions that map dependencies and consolidate shared understanding into a concrete plan with defined responsibilities.

How do I map dependencies when proposing a new feature or project?

To map dependencies for a new feature proposal, guide stakeholders through a structured interview that surfaces goals and constraints branch-by-branch, consolidating the context into a final summarized plan with risks and trade-offs.

Does structured plan design require specific input formats or prior documentation?

Structured plan design requires no specific input formats or prior documentation, but demands clear prompts and attentive responses during the interview to accurately surface goals, constraints, and dependencies.

What should I expect as the final output of a structured planning interview?

The final output of a structured planning interview is a summarized plan that explicitly documents all decisions, mapped dependencies, identified risks, and trade-offs reached during the branch-by-branch questioning process.