How does the 'Plan' agent different from standard Claude?

The 'Plan' agent is specifically prompted to challenge assumptions, dig into non-obvious technical threads, and batch questions efficiently to create a robust implementation roadmap.

What topics are covered during the interview?

The interview covers seven core areas: Requirements, Technical Implementation, UI/UX, Constraints, Tradeoffs, Scope Boundaries, and Validation.

When should I use the Feature Planning Interview skill?

Use this skill whenever you are starting a complex feature, a major refactor, or any task that requires thorough upfront planning to avoid technical debt.

Does this skill automatically generate code files?

No, the skill focuses on the planning and discovery phase. It will not write to files unless you explicitly request it to document the plan.

Feature Planning Interview

Name: Feature Planning Interview
Author: bendrucker

bybendrucker

•

Productivity & Workflow

Conducts comprehensive, structured interviews to architect and plan complex features before implementation begins.

About

The Feature Planning Interview skill acts as a dedicated architect for your development workflow. It engages you in a deep-dive dialogue to surface critical technical requirements, UI/UX considerations, and performance constraints that are often overlooked. By utilizing a specialized 'Plan' agent, it challenges assumptions and defines scope boundaries through intelligent question batching, ensuring that every edge case is considered and a solid technical foundation is established before any code is written.

Key Features

Success criteria definition to ensure clear validation and testing goals
Intelligent question batching to minimize context switching during discovery
Identification of technical tradeoffs and explicit scope boundaries
5 GitHub stars
Comprehensive analysis of UI/UX interactions, error states, and accessibility
Structured interview framework covering architecture, data flow, and APIs

Use Cases

Defining the architecture and data flow for a major system refactor
Mapping out user interactions and edge cases for a new product UI
Starting a complex new feature that requires deep technical coordination

About

Key Features

Success criteria definition to ensure clear validation and testing goals
Intelligent question batching to minimize context switching during discovery
Identification of technical tradeoffs and explicit scope boundaries
5 GitHub stars
Comprehensive analysis of UI/UX interactions, error states, and accessibility
Structured interview framework covering architecture, data flow, and APIs

Use Cases

Defining the architecture and data flow for a major system refactor
Mapping out user interactions and edge cases for a new product UI
Starting a complex new feature that requires deep technical coordination