writing-plans

To turn a spec into executable AI tasks, you convert requirements into a 2-3 task plan where each task specifies exact files, actions, verification steps, and done criteria for deterministic execution.

The 4-field task format for AI task planning structures each task with files, action, verify, and done fields, ensuring concrete execution steps and clear completion criteria within a 15-60 minute scope.

An AI execution plan should contain 2-3 tasks per context window, with each task scoped to 15-60 minutes of work to fit within a fresh context budget and maintain deterministic execution.

Yes, you can use this task planning approach for product and design workflows whenever a spec exists and you need concrete implementation steps with clear verification and completion criteria.

Common anti-patterns when creating multi-step task plans include exceeding the 2-3 task limit, poorly defined verification steps, and missing done criteria, which the plan templates and context budgeting guidance help prevent.

Yes, you need a complete written spec or requirements document before generating an executable task plan, as the planning process converts existing specifications into concrete files, actions, verifications, and done criteria.