Plan
Design the structure a B2B buyer actually needs, grounded in your value architecture and validated before a single page is written.
Why this skill
Listing pages is easy, but building a structure that covers every persona's job and every stage of the buying decision is the hard part, and it is where most sites leak. This step turns your value architecture into a validated site structure so the pages you build later each have a reason to exist.
What it does
It loads your value architecture (offerings, value drivers, capabilities, personas, customer profiles, metrics, case studies) and, when you point it at reference sites or competitor material, factors those in too. From that it produces a full page inventory: every page, its purpose, the persona it serves, the buying stage it covers, its one primary call to action, and the next step it leads to.
Before it writes anything, it checks the plan against a set of coverage tests. Every persona needs a page for the job they are trying to do, every stage of the buying process needs coverage, the homepage needs to tell a complete story, and every page needs exactly one primary call to action. The plan is only written once it passes.
The result is workspace/website/websitestructure.md, the single document that both the SEO and Generate steps read.
How to use it
Call /act-website-plan for a new site or to restructure an existing one. It asks a short set of setup questions up front, including language, whether the site is new or a restructure, your primary conversion goal, pages to exclude, whether you want competitor comparison pages, and any reference URLs. Then it does the rest. When it finishes it summarizes the plan and asks what you want to refine before you move on to SEO or Generate. It is standalone from the Audit, but the Generate step depends on its output.