idea-interview

Conducts a multi-round interview to turn vague ideas into project outlines.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/CMiller838/meal-planner --skill idea-interview-cmiller838
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-interview
Source: https://github.com/CMiller838/meal-planner/tree/main/.claude/skills/idea-interview
Command: npx skills add https://github.com/CMiller838/meal-planner --skill idea-interview-cmiller838

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New projects often start as vague ideas with no clear scope, leading to bloated feature lists and scope creep before any planning begins. This Skill runs a structured conversational interview that turns a rough idea into a concrete project outline with must-haves, nice-to-haves, constraints, and explicit non-goals. ## Core Features & Use Cases - Full Interview Mode: Runs multi-round, small-batch questioning covering problem, users, must-haves, constraints, and non-goals before any feature list exists. - MVP Guardrail: Challenges every proposed must-have to separate load-bearing features from nice-to-haves, resisting scope creep in the moment. - Single-Idea Mode: When an outline already exists, interviews about just one new idea and merges it into the outline or parks it in docs/FUTURE.md with a revisit trigger. - Use Case: A user says "I have an idea for an app but haven't fleshed it out." The Skill asks focused questions across several rounds, pushes back on an oversized must-have list, then writes a README project outline and parks deferred ideas in docs/FUTURE.md. ## Quick Start Help me think through this project idea I have and turn it into a concrete outline before we plan any features.

Frequently Asked Questions about idea-interview

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

FAQPage Schema
How do I turn a vague app idea into a project plan?

Use a structured interview process that asks about the problem, target users, must-have features, constraints, and non-goals in small batches of questions. The answers are then written up as a project outline document a collaborator could read cold.

How do I decide which features belong in an MVP?

For each proposed must-have, ask whether it blocks a usable first version or whether users could succeed without it. If the answer is only that it would be nicer to have, move it to the nice-to-have list or park it for later.

When should I use this instead of a project planner?

Use this before any feature list or roadmap exists, when the idea itself is still unformed. Once the project is scoped and outlined, planning individual phases is a separate planning task, not an interview.

What happens to feature ideas that are out of scope?

Deferred ideas are appended to a docs/FUTURE.md file with a one-or-two sentence description, the reason they were parked, and a concrete trigger for revisiting them, such as after v1 ships or once there are paying users.

Can I add a single new idea to an existing project outline?

Yes, a lighter single-idea mode reads the existing outline and FUTURE.md first, asks one round of placement questions, then either adds the idea to the feature list or parks it, without re-running the full interview.