Plan Philosophy

Write as if the executor is an enthusiastic junior engineer with no project context.

Every step must be self-contained and unambiguous. If someone has to guess what you meant, the plan failed.

Step Requirements

Each step in the plan must include:

Exact file paths — Full paths to every file that will be created or modified.
Function signatures with types — The exact function names, parameter types, and return types.
Data flow — Where data comes from, how it transforms, where it goes.
Error handling strategy — What errors can occur and how each is handled.
What NOT to change — Explicitly call out nearby code that must remain untouched.
Verification criteria — How to confirm this step is done correctly (test command, expected output, etc.).

Author implementation plans that can be executed without ambiguity.

Write as if the executor is an enthusiastic junior engineer with no project context.

Every step must be self-contained and unambiguous. If someone has to guess what you meant, the plan failed.

Each step in the plan must include:

Exact file paths — Full paths to every file that will be created or modified.
Function signatures with types — The exact function names, parameter types, and return types.
Data flow — Where data comes from, how it transforms, where it goes.
Error handling strategy — What errors can occur and how each is handled.
What NOT to change — Explicitly call out nearby code that must remain untouched.
Verification criteria — How to confirm this step is done correctly (test command, expected output, etc.).