Run any Skill in Manus with one click

pre-launch-checklist

Stars4

Forks0

UpdatedJuly 10, 2026 at 22:26

The go-live gate for websites, tuned for German/EU agencies — legal compliance (DSGVO/GDPR, Impressum, Cookie-Consent, BFSG accessibility) plus the technical launch checklist (SSL, redirects, 404, OG tags, sitemap, robots, forms, analytics). Use this skill before ANY website goes live or relaunches — trigger on "pre-launch", "go-live check", "launch checklist", "können wir live gehen", "ready to launch?", "vor dem Launch prüfen", "Website abnehmen", or when the agency-workflow LAUNCH phase runs. Legal items are hard blockers, not warnings. Not a general QA pass (use performance/accessibility/webapp-testing for that) — this is the final gate after QA.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Gekkos-tech

Gekkos-tech/agency-os

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name

pre-launch-checklist

description

Pre-Launch Checklist

Run this as the last gate before DNS cutover. Two sections: legal (hard blockers — a German site going live without these creates liability) and technical. Produce docs/launch-checklist.md with pass/fail + evidence per item. Anything failing legal = no launch recommendation, stated plainly.

A. Legal (DACH/EU) — hard blockers

Impressum (§ 5 DDG, formerly TMG)

Impressum page exists, reachable from EVERY page within 2 clicks
Contains: full legal name + legal form, postal address (no P.O. box), email AND a second fast contact channel (usually phone), authorized representative, commercial register + number (if registered), USt-IdNr. (if assigned), supervisory authority / chamber for regulated professions
Responsible person for editorial content (§ 18 Abs. 2 MStV) if the site has journalistic/editorial content

Datenschutzerklärung (DSGVO)

Privacy policy page linked from every page, current, and matching what the site ACTUALLY does — verify against reality:
- every third-party service found in the code/network tab is listed (fonts, maps, analytics, tag manager, video embeds, forms, CDN, chat)
- legal basis named per processing purpose
- data subject rights, retention, controller contact, Datenschutzbeauftragter (if required)
Google Fonts are self-hosted (loading from fonts.googleapis.com is an established Abmahnung risk in Germany), same logic for other third-party assets that leak IPs pre-consent
Forms: only necessary fields, HTTPS submission, no pre-checked marketing checkboxes, double opt-in for newsletters

Cookie-Consent (TDDDG § 25 + DSGVO)

No non-essential cookies/storage before consent — verify in DevTools with a fresh profile: only technically necessary items pre-consent
Analytics/marketing tags fire only AFTER opt-in (test both paths)
Banner: "Reject all" as prominent as "Accept all", granular choices, consent revocable (persistent link/settings), no dark patterns
If only essential cookies are used: no banner needed — do not add one "for safety"; document it instead

BFSG (Barrierefreiheitsstärkungsgesetz, in force since 2025-06-28)

Determine applicability: B2C e-commerce, booking/reservation systems, and consumer-facing digital services generally in scope (micro-enterprise exemption < 10 employees AND ≤ 2M € turnover — services only). Document the assessment either way.
If in scope: WCAG 2.1 AA conformance (EN 301 549) — run the accessibility skill and fix blockers
"Erklärung zur Barrierefreiheit" (accessibility statement) published

B. Technical

Security & transport

SSL certificate valid for apex + www; auto-renewal configured
HTTP → HTTPS redirect; no mixed content (check console)
Security headers: HSTS, X-Content-Type-Options, Referrer-Policy, sensible CSP (or documented why not)

Redirects & URLs

Relaunch: every indexed old URL 301-mapped (crawl old site / Search Console export first); spot-check top-20 pages
www vs non-www: one canonical host, the other redirects
Trailing-slash behavior consistent
Custom 404 page: helpful, branded, links back; returns real 404 status

Discoverability

robots.txt present and NOT blocking the site (the classic staging-robots-goes-live failure — check explicitly)
No stray noindex from staging (meta or X-Robots-Tag)
XML sitemap generated, referenced in robots.txt, submitted to Search Console; contains only canonical, 200-status URLs
Canonical tags correct; per-page unique titles + meta descriptions
OG tags + Twitter cards on all shareable pages; og:image exists in 1200×630 and actually renders (test with a share debugger)
Favicon set + web manifest; schema markup for the business type (LocalBusiness with NAP for local clients)

Function & content

All forms submit successfully AND the mail/CRM actually receives them (send real test submissions)
All internal links + nav work; no dead anchors; external links open correctly
Real content everywhere: no lorem ipsum, placeholder images, or example@... addresses; phone numbers and opening hours correct
Analytics installed, consent-gated, and recording (verify a test pageview post-consent); goals/conversions configured

Ops

Backup/rollback plan for the cutover; DNS TTL lowered in advance
Monitoring/uptime check on the live URL
Post-launch hour-one verification list ready (live URL mobile+desktop, forms, consent, Search Console sitemap fetch)

Output format

# Launch-Checkliste — {project} — {date}
## Ergebnis: GO / NO-GO (Blocker: n)
| # | Item | Status | Evidenz/Notiz |
...
## Blocker (müssen vor Launch behoben werden)
## Empfehlungen (nach Launch)

Write the client-facing report in the client's language. This checklist is a practical launch aid, not legal advice — recommend a lawyer's review for regulated industries (health, finance, legal services).

More from this repository

same repository

agency-workflow

Gekkos-tech/agency-os

The agency project router — orchestrates the full client-project lifecycle BRIEF → CONCEPT → DESIGN → BUILD → QA → LAUNCH plus the post-launch MAINTAIN loop, and tells Claude which specialist skill to load at each phase. Use this skill whenever a client web project starts or advances — trigger on "new project", "neues Projekt", "website for a client", "Website für Kunde/Kunden", "Kundenprojekt starten", "start a client project", "we won a pitch", "relaunch for", "where does the project stand", "wo steht das Projekt", or any request to plan, kick off, continue, or maintain a client website, landing page, or web app — even if the user only describes the client and goal ("a website for a café in Cologne"). This skill routes, enforces phase gates, and keeps docs/project-state.md current; the actual design/build/QA work happens in the specialist skills it delegates to.

2026-07-124

cms-integration

Gekkos-tech/agency-os

Choose and integrate the right CMS for a client website — decision tree (client editing needs, budget, hosting, stack) plus integration patterns for Payload, Sanity, Storyblok, Strapi, Decap, and headless WordPress, and a client-handover checklist. Use when the user asks "which CMS", "add a CMS", "the client wants to edit content themselves", "Kunde soll Inhalte selbst pflegen", "WordPress or something modern", "headless CMS", or when the BUILD phase reveals editable content requirements. Covers selection, modeling content from the design handoff, preview setup, and editor training. NOT for building the site's frontend (BUILD phase skills), NOT for content strategy or SEO content (seo-content), NOT for one-off static sites where nothing needs client editing — recommending "no CMS" is a valid outcome of this skill.

2026-07-124

impeccable

Gekkos-tech/agency-os

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks; GSAP/scroll animation implementation belongs to gsap-suite (motion-3d).

2026-07-124

ad-concepts

Gekkos-tech/agency-os

Generates advertising campaign concepts and creative routes. Use when the user asks for a "campaign for" / "Kampagne für" a product, "ad ideas", "campaign ideation", "creative concepts for ads", "hook ideas", or wants creative directions before production. Always delivers exactly 3 distinct campaign routes (working title, core claim, hook, visual idea, primary channel, persuasion framework) built on an audience-insight step and a framework toolbox (AIDA, PAS, JTBD, 4U, hook formulas). NOT for writing finished ad copy or headlines (use ad-copy), NOT for platform format specs or asset dimensions (use social-formats), NOT for landing page structure (use landingpage-cro).

2026-07-104

ad-copy

Gekkos-tech/agency-os

Writes performance ad and landing page copy in German and English. Use when the user asks for "ad copy", "Werbetext", "headlines for", "CTA ideas", "A/B variants", "copy for the campaign", or needs finished text for Meta/Google/LinkedIn ads, landing pages, or banners. Provides headline systems (benefit, curiosity, social-proof, urgency), a funnel-stage CTA library (DE+EN), an A/B/C variant protocol with per-variant hypotheses, a tonality matrix, German-specific rules (Du/Sie, compound words, character lengths), and compliance guardrails. NOT for campaign ideation or creative routes (use ad-concepts), NOT for long-form content strategy, blog posts, or SEO articles (use seo-content skills).

2026-07-104

landingpage-cro

Gekkos-tech/agency-os

Structures and audits landing pages for conversion — the bridge between design, SEO, and copy. Use when the user asks about "landing page structure", "CRO", "conversion optimization", "why isn't the page converting", "landingpage aufbauen", or needs a section-by-section page architecture, friction audit, message-match check, or A/B testing plan. Covers the conversion narrative sequence (hero → credibility → problem/solution → offer → proof → objections → risk reversal → CTA), DACH trust elements, mobile-first conversion rules, and a measurement plan. NOT for visual design systems, typography, or component styling (use design-foundation skills), NOT for SEO audits, rankings, or keyword research (use seo-marketing skills), NOT for writing the copy itself (use ad-copy).

2026-07-104