create-plan

To break down a coding task, you can generate a structured plan that organizes the request into intent, scope, and ordered action items. This method transforms vague prompts into concise, actionable checklists for task execution.

Planning a refactoring workflow is best done by generating a structured plan that outlines steps from discovery and implementation to testing. This approach creates clear action items and defines the scope to ensure focused execution for the web app component.

The planning process only outputs actionable checklists and does not generate code automatically. It operates in read-only mode, focusing entirely on structuring the task breakdown, defining intent, and highlighting open questions rather than handling the actual implementation.

Yes, you can use this task breakdown approach for adding new user authentication features. It will generate a plan detailing steps from discovery and implementation to testing and rollout, ensuring all action items and open questions are clearly defined before coding begins.

The planning mechanism handles missing context by asking minimal follow-up questions. After scanning the available context, it identifies gaps and requests necessary clarification to structure the output accurately with intent, scope, action items, and open questions.