plan-feature

To break down complex Rails feature requests, you must gather requirements, analyze the codebase, and produce a structured list of database, controller, view, and testing tasks. This reduces ambiguity by aligning the implementation plan with existing project conventions.

The best way to plan a new Rails feature is to ask targeted clarification questions based on the feature type, scan models and routes, and generate an ordered task list. This ensures all database, business logic, and testing requirements are captured before development starts.

Preparing a task breakdown for CRUD operations involves scanning your Rails codebase for existing patterns and generating ordered tasks for migrations, controllers, views, and tests. This structured approach ensures dependencies and risks are identified before coding begins.

Yes, this feature planning approach works for Rails APIs and Turbo integration by asking 2 to 4 specific clarification questions depending on the feature type. It analyzes your routes and frontend setup to produce tailored implementation tasks for your API or Turbo dashboard.

You should expect 2 to 4 targeted clarification questions when planning a Rails project, depending on whether the feature involves authentication, CRUD operations, dashboards, or APIs. This focused requirement elicitation informs the final database and controller tasks.