Launch Readiness

What it does

Classifies and verifies what customers, search engines and operators actually need before a production launch.

When to use it

Use before client approval, indexing or deployment, to decide what's required, optional, or blocked by missing information.

Problems it prevents

Stops launches blocked by nobody realising a required business or legal fact was never actually supplied.

Typical workflow

1. Classify each requirement's applicability
2. Verify what's actually been built
3. Flag what's blocked by missing facts
4. Report without fabricating content

Example output

A launch checklist split into required, optional, not-applicable and blocked, with blocked items named honestly.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• SystemSecurity

  Applies the evidence-based production security gate across secrets, auth, data access, uploads, dependencies and APIs.

• SystemSEO

  Implements and audits technical and on-page SEO: titles, canonicals, sitemaps, robots, social metadata, structured data, internal links.

• SystemWebsite Final Audit

  Orchestrates the final evidence-based quality gate: anti-vibecode, production security and launch-readiness checks combined.