prometheus

To turn an ambiguous feature idea into a safe execution plan, use intent classification to run targeted codebase discovery and conduct clarifying interviews before implementation. This generates a structured plan with test strategy, tasks, and explicit exclusions for safe handoff to an executor workflow.

The best way to plan a refactoring task without breaking behavior is to conduct pre-research on the codebase to scan existing patterns and tests. This plan-first workflow generates a structured execution plan with a defined test strategy and anti-pattern avoidance before any code is written.

Intent classification helps with software design and architecture decisions by categorizing requests into refactor, build-from-scratch, architecture, or research tasks. This ensures the system asks only the necessary clarifying questions and conducts targeted codebase discovery before finalizing decisions.

Yes, you can use a plan-first workflow for building a new authentication system from scratch. It classifies the build intent, runs pre-interview exploration to assess test infrastructure, and generates a structured execution plan with tasks and exclusions before implementation begins.

You need to conduct pre-research and codebase analysis before coding when scope and constraints must be clarified for complex changes. This applies to refactoring, building from scratch, architecture decisions, and research-driven tasks where safe pre-interview exploration prevents anti-patterns.