When the featues of a task are being define, these steps need to be followed:

Each task must be completable in ONE Ralph iteration (~one context window).

The agent should start with a new instance with no memory of previous work. If a task is too big, the LLM runs out of context before finishing.

Right-sized tasks:
- Add a database column + migration
- Create a single UI component
- Implement one server action
- Add a filter to an existing list
- Write tests for one module

Too big (split these):
- "Build the entire dashboard" → Split into: schema, queries, components, filters
- "Add authentication" → Split into: schema, middleware, login UI, session handling
- "Refactor the API" → Split into one task per endpoint

Rule of thumb: If you can't describe the change in 2-3 sentences, it's too big.

We want to make sure that this principle is followed by the agent for all tasks and features so make sure this way of thinking is part of the plan.md

