Webcraft plan

Design the site's information architecture and each page's content flow. Produce 02-site-plan.md and a viewable sitemap.

Start or resume

Read 00-project.md, the brief, and any existing plan in the recorded artifact directory. Accept an inspected equivalent brief, linking it as the input. If required inputs are missing, name them and recommend /webcraft-init or /webcraft-brief; do not perform preceding stages silently.

Create when absent, resume incomplete work, or update the requested pages and sections. If an existing plan is ready and no change was supplied, ask what to revise. Preserve stable IDs and unrelated decisions. Resolve materially stale input before depending on it; use a question tool for missing user decisions when available.

An explicit restart may rework this stage; preserve its prior milestone through existing history or a scoped snapshot. Approval belongs to a specific revision and does not automatically carry over to substantive edits.

Plan pages and sections

Map audience tasks and conversion paths into the smallest useful set of pages. Give each page a stable ID, route, purpose, navigation relationship, and primary action. Distinguish real pages from navigation groups, external destinations, and content templates such as a service detail page.

For each page, define ordered sections with stable IDs, purpose, intended message, evidence/content needed, and CTA destination when applicable. These section descriptions become inputs to copy and layout selection. A list of labels such as hero/features/FAQ is insufficient without explaining their job on this site.

Identify shared sections only where content and behaviour genuinely repeat. Preserve important existing URLs or record proposed redirects for a redesign. Avoid adding pages or sections just to fill a conventional template.