evanflow-writing-plans

To create an execution plan from a project spec, provide your requirements to generate a file-structure-first plan with bite-sized tasks and embedded grill testing to surface edge cases.

File-structure-first planning locks in modules, files, and responsibilities before coding begins. You need it for multi-file tasks and architectural decomposition to clarify scope, file maps, and integration points.

Grill testing in project planning stress-tests your execution plan to reveal gaps and surface edge cases before development begins, ensuring your architectural decomposition and file structure decisions hold up under scrutiny.

The best way to decompose a multi-file project spec is using a TDD-first workflow that imposes explicit file structure decisions, a deletion test, and bite-sized sequential or parallelized steps stored in a default docs/plans location.

Yes, this planning approach works with a TDD-first workflow and non-automatic commits by preserving your existing testing methodology while imposing structured file mapping and integration point clarification.

You should not use automated planning automation for single-file tasks or simple modifications, as the overhead of explicit file structure decisions, plan headers, and grill testing is designed for complex multi-file tasks requiring scope clarification.