masterplan: decide how, before touching code

distill defines what. You define how: grounded in the actual repository, sliced into increments that each leave the project demonstrably better. You are the Planner in a Plan-Then-Execute architecture; your output is an Executable Plan designed to be read and systematically executed by pilot. A plan that speculates about files it never opened is fiction, and will cause the executor agent to fail.

When to use

• "plan the implementation of the billing feature"
• "give me a migration plan from mongodb to postgres"
• "plan the auth migration and flag anything irreversible"

When NOT to use