discovery-interrogation

Interviews the project owner one question at a time and writes a Discovery.md artifact before planning.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill discovery-interrogation-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-interrogation
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/discovery-interrogation
Command: npx skills add https://github.com/timikalo7/Execute --skill discovery-interrogation-timikalo7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans built on assumptions get rejected at approval gates and waste research passes. This Skill extracts the owner's actual intent through a structured one-question-at-a-time interview before any research, planning, or building begins, so downstream agents work from confirmed decisions instead of guesses. ## Core Features & Use Cases - Guided interrogation method: Asks one question at a time with a recommended answer, walking the decision tree so high-impact forks are resolved first. - Scoped question branches: Covers outcome and scope, users and value, budget/timeline/runtime constraints, security gate profile, data and integrations, design voice, and explicit out-of-scope items. - Discovery.md artifact: Writes answers, stated assumptions, plan implications, and open questions to potential-projects/<name>/Discovery.md, which research, viability, plan, and build agents then read. - Non-interactive fallback: When the owner cannot answer, marks every needed answer as ASSUMED — unconfirmed and surfaces them in the YOU DO list instead of stalling. - Use Case: At the start of a /kickoff for a new product idea, run this Skill to grill the owner on budget, target users, and must-not-change constraints, producing a Discovery.md that the research and viability agents consume. ## Quick Start Before planning my new project idea, interview me one question at a time about scope, users, and constraints, then write the results to Discovery.md.

Frequently Asked Questions about discovery-interrogation

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

FAQPage Schema
How do I gather project requirements before writing a plan?

Run a structured discovery interview that asks the owner one question at a time, each with a recommended answer, covering scope, users, constraints, and risks. Record the confirmed answers and assumptions in a Discovery.md file that planning agents read.

What questions should I ask before starting a new software project?

Ask about the v1 definition of done, target users, budget and timeline constraints, runtime surface, whether the project touches auth or payments, required data and integrations, design references, and what is explicitly out of scope.

When should discovery interrogation run in a planning workflow?

Run it at the start of a kickoff before any research, and before non-trivial feature additions, improvements, or redesigns. It must complete before research and viability agents begin, since they score against the owner's real goals.

What happens if the owner cannot answer discovery questions?

The run does not stall. Every needed answer is marked ASSUMED — unconfirmed in Discovery.md, work continues on those assumptions, and the assumptions are surfaced in the YOU DO list so the owner can correct them in one pass.

Why do AI-generated project plans get rejected at approval?

Plans built on agent assumptions rather than owner intent fail approval gates and waste research passes. A discovery interview extracts decisions from the owner first, so every plan choice traces to a confirmed answer or a stated assumption.