It can help with complicated tasks. When prompting via the chat interface, it comes more naturally to prompt with a full description of the problem. With too m

It can help with complicated tasks. When prompting via the chat interface, it comes more naturally to prompt with a full description of the problem. With too much assumed context, it only does a good job of spitting out the answer to a common problem, or implementing a mostly correct version of the commonly written task similar to the one requested. When you use copilot, are you shaping your use to its workflows? Adding preceding comments to describe the high-level goal, the high-level approach, and other considerations for how the code soon to follow interacts with the rest of the codebase?