Plan mode prompt encourages too much example code

[monneyboi]

Problem

The plan mode prompt:

[Plan mode active] You may only edit/write files under .pi/plans/. Use read and bash freely to explore. When the plan is ready, run /approve.

This gives no guidance on what kind of plan to write, so agents produce plans full of detailed example code and diffs — which defeats the purpose of planning at a high level.

Proposed fix

Steer toward high-level, prose-based plans:

[Plan mode active] You may only edit/write files under .pi/plans/. Use read and bash freely to explore. Write a high-level plan — describe what to change and why, not how. No example code or diffs; save that for the implementation. When the plan is ready, run /approve.