Preparing a Project Launch

A launch is ready when a new visitor can understand the project, try or install it, and get help if a step fails. Inspect the deployed product or distributable, repository, documentation, and intended primary action; do not infer readiness from a passing build alone.

Workflow

1. Identify the intended audience, launch goal, primary CTA, target channels, and exact release or commit. Distinguish a new project from a feature update. Ask for missing access only when it blocks verification.
2. Walk the visitor path from the launch link to the first useful outcome. Verify live links, public access, installation steps, sample data, responsive presentation, and the actual download or signup action using the available environment. Record which checks cannot be performed.
3. Inventory claims, screenshots, demo flows, prices, availability, version, platform support, and credits. Match each meaningful promise to inspectable product behavior or documented evidence. Mark unverified claims for correction; never manufacture usage numbers, testimonials, or metrics.
4. Check whether the public surfaces have a usable title, description, social preview, accessible media alternatives, legal/privacy links when the product requires them, and a clear path to report problems. Avoid adding bureaucracy to a small open source release.
5. Produce a launch brief: audience, one-sentence value, differentiator, primary CTA, two or three real demonstration moments, approved proof, asset inventory, unresolved blockers, and the exact links. Rank blockers by whether a visitor can complete the promised action.
6. Verify the fixed blockers against the same release. Keep evidence tied to its date and version; avoid calling a feature stable just because its marketing materials exist.

Handoff

Pass the verified brief to brag-slim for a video, building-project-showcases for durable presentation, and planning-launch-distribution for channel-specific release work. This method owns readiness and truthful claims, not the video's editing, page design, deployment, or the launch schedule.