create-plan

To break down a complex coding task into an implementation plan, generate a structured document featuring an objective, checkbox-formatted steps, verification criteria, risks, and alternative approaches.

The best way to structure technical documentation before development is to use a strict plan format that includes objective, risk assessment, verification criteria, and a checkbox-based step-by-step implementation roadmap.

You validate a project strategy and task breakdown by running an included validation script against the generated plan file to ensure it meets the required structural quality and compliance standards.

Yes, this planning approach requires specific risk management steps, enforcing a strict structure where you must explicitly document potential risks and their corresponding mitigations before execution.

Yes, you can use this for generating a roadmap as it explicitly requires documenting alternative approaches alongside the primary implementation plan to ensure comprehensive strategy evaluation.

A limitation of using a checkbox-based task breakdown is that it requires a rigid plan structure, meaning you must validate the generated document with a specific script before proceeding to actual execution.