plan-feature

Capturing software requirements and edge cases requires a structured Socratic dialogue that surfaces intent, scope, and constraints. This approach forces explicit rationale for every behavior, producing a standardized markdown plan artifact before any implementation begins.

Socratic feature planning is a structured conversation that guides developers through intent discovery and edge case exploration. It coaxes missing context for new API endpoints, UI interactions, or infrastructure changes, ensuring functional and non-functional requirements are documented without producing code.

Documenting functional and non-functional requirements requires exploring behaviors, failure modes, and locked-in decisions through guided questioning. This method prevents vague briefs by forcing explicit rationale for constraints, yielding a complete feature plan artifact for downstream engineers.

Using this planning method to align on API endpoint scope ensures intent and constraints are explored without drifting into task generation. It applies specifically when a developer needs to understand scope and document decisions before any coding or task generation occurs.

The best way to plan a single feature and avoid vague briefs is a Socratic dialogue that captures requirements, edge cases, and decisions. This process produces a standardized markdown planning artifact that keeps subsequent workflows focused, grounded, and efficient.

Socratic dialogue for feature planning should not be used when code generation or task breakdown is the immediate goal. The process strictly focuses on understanding intent, documenting constraints, and capturing decisions, deliberately excluding implementation and task generation outputs.