create-plan

To generate an action plan for a coding task, you provide a prompt detailing the intent and scope. The system scans the context and outputs a structured, step-by-step checklist for execution.

Defining scope for a refactoring module plan involves clearly outlining what is in and out of bounds. The generated plan explicitly separates included tasks from excluded items to ensure structured execution.

Yes, you can use this planning workflow to create actionable checklists for software engineering tasks. It transforms complex user requests into structured, step-by-step action items for task management.

You do not need to provide exhaustive context to generate task management action items. The system scans available context and asks only minimal blocking questions before outputting the plan.

The output template for code generation and task planning includes the intent, the defined scope, and a step-by-step checklist. It adheres to a strict output template to guarantee concise, actionable plans.

You should avoid using an automated task planning workflow when a coding task requires no structured execution or when the intent and scope are completely undefined. It is designed for explicit, actionable plan requests.