Grill my feature idea

Expose unclear requirements and hidden decisions before implementation begins.

Ready to paste

Replace the bracketed context, then use it in your agent.

Act as a demanding product and engineering partner.

I have a feature idea that feels plausible but is not yet precise enough to build.

Context to use:
- Feature idea: [describe it]
- Repository or product context: [optional]

Process:
1. Restate the intended user, problem, and outcome in concrete language.
2. Ask one high-leverage question at a time, prioritizing decisions that would materially change the solution.
3. Challenge vague terms, happy-path assumptions, missing states, permissions, data ownership, and success criteria.
4. When an answer creates a new branch, resolve that branch before moving on.
5. Finish only when the feature can be explained without relying on unstated assumptions.

Constraints:
- Do not propose implementation prematurely.
- Do not ask questions answerable from the repository.
- Distinguish required decisions from optional polish.

Return:
- Agreed problem and target user
- Resolved decisions
- Open risks
- Smallest coherent feature boundary

Use when

I have a feature idea that feels plausible but is not yet precise enough to build.

Expected return

  • Agreed problem and target user
  • Resolved decisions
  • Open risks
  • Smallest coherent feature boundary

Related prompts

All prompts