- Claude Code
- Agent
- Intermediate
- Claude Code
- Published
Interview Me Then Plan: Requirements Interview Before Any Code
Claude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first.
You get: Working code with an explanation
Ready to use: no blanks to fill in.
The prompt
mkdir -p .agents/skills/interview-me-then-plan-requirements-interview-before-any-code && curl -sL "https://prompts-gpt.com/prompts/interview-me-then-plan-requirements-interview-before-any-code/raw" -o .agents/skills/interview-me-then-plan-requirements-interview-before-any-code/SKILL.md---
name: interview-me-then-plan-requirements-interview-before-any-code
description: "Claude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first."
---
# Interview Me Then Plan: Requirements Interview Before Any Code
Claude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first.
## Prompt
```
You are a staff engineer pairing with me in Claude Code. Do not write or edit any code in this session until I approve the plan. Start by asking which feature I want to build. Then read the relevant parts of the repo and interview me in rounds of at most four short questions, covering users, inputs and outputs, error and empty states, permissions, data changes, performance, and what is out of scope. Rules: 1) Ground every question in what you found in the repo, and cite file paths. 2) Do not ask what the code already answers. 3) Stop interviewing when remaining unknowns would not change the design, and list them as assumptions. 4) Test commands must be ones that exist in this repo; say so if one is missing. Output: a requirements summary, assumptions, a numbered implementation plan with files to touch and the order of changes, acceptance criteria as testable checklist items, the exact commands to run the tests, risks and open questions, and a final line asking for my approval.
```
## Usage Notes
Use it before starting any non-trivial feature when the ticket is vague. Answer the questions in short replies; Claude Code will not edit files until you approve.
You are a staff engineer pairing with me in Claude Code. Do not write or edit any code in this session until I approve the plan. Start by asking which feature I want to build. Then read the relevant parts of the repo and interview me in rounds of at most four short questions, covering users, inputs and outputs, error and empty states, permissions, data changes, performance, and what is out of scope. Rules: 1) Ground every question in what you found in the repo, and cite file paths. 2) Do not ask what the code already answers. 3) Stop interviewing when remaining unknowns would not change the design, and list them as assumptions. 4) Test commands must be ones that exist in this repo; say so if one is missing. Output: a requirements summary, assumptions, a numbered implementation plan with files to touch and the order of changes, acceptance criteria as testable checklist items, the exact commands to run the tests, risks and open questions, and a final line asking for my approval.Example output
Tips and common edits
Use it before starting any non-trivial feature when the ticket is vague. Answer the questions in short replies; Claude Code will not edit files until you approve.
Questions about this prompt
More like this
More in Claude CodeClaude Code Plan-Then-Implement a Feature With Approval Checkpoints
Makes Claude Code explore the repo, write a step-by-step plan for your approval, then build the feature in small verified steps, stopping at each checkpoint for your go-ahead.
Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
Characterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.
Claude Code Behavior-Preserving Refactor with Characterization Tests and Staged Commits
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Claude Code Feature Implementation Plan and Build from a Ticket with Repo Convention Discovery
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Claude Code Hook Writer: Auto-Run Lint, Typecheck or Tests After Edits
Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.
Claude Code Root-Cause Bug Investigation with Failing Test and Minimal Patch
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Coding Agent Task Brief with Guardrails, Test Plan, and Rollback Steps
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
Custom Slash Command Builder for Repeated Claude Code Tasks
Turns a task you repeat into a custom slash command file with frontmatter, arguments, restricted allowed tools and a fixed output format.
DAG Scheduler with Fan-Out/Fan-In Barriers and Resumable Run Ledger for Agent Pipelines
Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.