plan: scope it properly, or don't build it at all

Every initiative gets ONE file that travels its whole life:

 idea ──> survived ──> planned ──> executing ──> reviewed ──> banked
              ^            ^
          the gauntlet  THIS SKILL

Plan owns the planned arrow. Work that reaches sprint without passing through here does not run. That refusal is the whole point of the collection, and this skill is where it lives.

Before any step, read references/CONVENTIONS-core.md. This resolves from the installed skill directory to the plugin's shared contract; the founder's working folder is never used to locate it. Its state, receipts, filing, and dedupe rules govern this workflow.

Step 0: Load the ground