plan-websitelisted

Creates a Work Breakdown Structure for planning and executing a website build from scratch or as a migration/overhaul. Organizes repository setup, planning artifacts, implementation slices, QA gates, and launch work into deliverables, work packages, and tasks, with phase checklists as supporting artifacts. Use when the user mentions building, launching, or overhauling a website: redesigns, CMS migrations, new site builds, or multi-team web projects. Triggers on phrases like "website build", "site launch", "web project checklist", "website redesign", "launching a site", "new website", or "website planning". Also use when the user wants to know what documents or deliverables a web project needs, or is coordinating design, dev, content, and SEO teams on a site.
datashaman/code-skills · ★ 1 · Web & Frontend · score 68

Install: claude install-skill datashaman/code-skills

# Plan Website - WBS-led website delivery planning A website build (not just a redesign — if structure, content types, or CMS change, it's a build) is a multi-month, cross-team project. This skill creates a Work Breakdown Structure (WBS) that carries the project from repository foundation through planning artifacts, implementation slices, verification, and launch. **Important distinction:** A *redesign* only re-skins an existing site. If content types, URL structure, database, or CMS change at all, it's a **build** — treat it accordingly. ## Phase order Always walk through phases in this order. Each phase is a dependency for the next. 0. Discovery 1. Sitemap 2. Content Strategy 3. Wireframes 4. Designs 5. Analytics Implementation Plan 6. SEO Implementation Plan 7. Development 8. QA & Launch ## How to use this skill When a user comes with a website build question: 1. **Identify the project type and current phase** in the dependency sequence. 2. **Create or preserve the WBS** as the source of truth for build plans, delivery plans, roadmaps, Growth projects, Jira epic lists, or implementation checklists. 3. **Surface the right questions** for the current phase (see per-phase sections below). 4. **Flag missing dependencies** — if they're in Phase 4 but have no signed-off wireframes, flag it. 5. **Attach supporting artifacts** to WBS items — checklists, template lists, brief outlines, review criteria, entry criteria, exit criteria, and sign-off gates. 6. **Don't let teams