Do you prefer to receive tasks in a decomposed or abstracted form?

I prefer to receive tasks with a reasonable level of decomposition — so that the final goal and main steps are clear, but there is still room for independent choice of approach and optimizations.

Too abstract tasks can lead to uncertainty and loss of time on clarifications, while overly detailed ones limit flexibility and initiative.

For example, if a task is to "implement an API for user management with CRUD," it's good if there is a description of the main endpoints and requirements, but implementation details (architecture, choice of libraries) can be decided independently. This allows leveraging experience and finding the best solutions.