intake-interview

Name: intake-interview
Availability: InStock
Author: velcrafting

Interview stakeholders to generate a structured Intake Brief with bounded questions.

1|Updated Jan 13, 2026

Search Tags:#requirements #clarity #discovery #interview #product-management #stakeholders #intake-brief

Ready to run

npx skills add https://github.com/velcrafting/codex-skills --skill intake-interview

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intake-interview
Source: https://github.com/velcrafting/codex-skills/tree/main/skills/meta/intake-interview
Command: npx skills add https://github.com/velcrafting/codex-skills --skill intake-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview to extract intent, constraints, assumptions, and success criteria for a new system or major feature. Produces an Intake Brief (not a plan, not code).

Core Features & Use Cases

Bounded interview process (up to 10 questions) to surface critical decisions.
Structured Intake Brief output with sections for Objective, Users, Success metrics, Constraints, Requirements, Assumptions, Open questions.
Safe, read-only operation that avoids implementing plans or architectures.

Quick Start

Run an intake interview to generate a complete Intake Brief from the project goals and constraints.

Frequently Asked Questions about intake-interview

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

FAQPage Schema

How do I gather stakeholder requirements for early-stage product discovery?▼

Gather stakeholder requirements for product discovery by running a bounded intake interview that asks up to 10 targeted questions, capturing ambiguity and extracting intent without generating implementation plans.

What is the best way to document project goals and constraints before planning?▼

Document project goals and constraints before planning by generating a structured Intake Brief, which formally records the Objective, Users, Success metrics, Constraints, and open questions gathered during stakeholder interviews.

How does a stakeholder intake interview process work for feature initiatives?▼

A stakeholder intake interview for feature initiatives works by enforcing a read-only operational scope, asking a maximum of 10 questions to surface critical decisions, and outputting a formal Intake Brief rather than code or architecture.

Can I use an intake brief to capture success metrics and assumptions for a new system?▼

Yes, you can capture success metrics and assumptions for a new system using an Intake Brief, which includes specific sections for Success metrics, Assumptions, Constraints, Requirements, and Open questions to document the initiative.

What are the limitations of using an intake interview for requirements discovery?▼

The limitations of an intake interview for requirements discovery include a strict boundary of 10 questions and a read-only operational scope, meaning it produces an Intake Brief but will not generate implementation plans, architectures, or code.