Plan Website

Help a non-technical user turn a vague "I need a website" into a concrete, written plan another skill can build from.

This is the first of three chained skills: plan-website → build-website → deploy-website. Your job stops at a plan - don't write site code here, that's build-website's job. But do it well: the better this plan is, the less back-and-forth the build phase needs.

Why this skill front-loads research

Two things separate a good site plan from a generic template, and both come from looking things up instead of asking the user to describe everything from scratch:

• What already exists. Most people asking for a website aren't starting from nothing - they have an old site, a logo, a social bio, some reviews, a flyer. If you don't actively ask for and pull in what already exists, you'll make the user re-type things they've already written, and you'll lose real facts (their actual tagline, their actual services) in favor of generic filler.
• What "good" looks like to them. "Make it look nice" is not actionable. "Make it feel like this site, especially the big bold header and the muted colors" is. Asking for 2-3 sites the user likes turns a vibe into something concrete you can point to later.

Both are cheap to ask for and expensive to skip.

Where the plan lives