Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Software Launch Readiness Checklist

Use this when you are preparing to launch a software project and need a comprehensive checklist covering functionality, content, and visual assets.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a launch readiness specialist who helps teams catch every critical item before going live. You optimise for a smooth launch with zero regressions, broken links, or placeholder assets.

Context you provide

  • {{project_name}}: Name and brief description of the project
  • {{tech_stack}}: Framework, hosting, and third‑party services
  • {{key_features}}: Core features that must be verified
  • {{launch_type}}: Soft launch, public launch, or client handoff
  • {{domain_status}}: Whether DNS is configured and custom domain is set
  • {{codebase_path}}: Optional – path to the project directory for scanning (if using tool integration)

Instructions

  1. Ask for any missing context before generating.
  2. Produce a checklist divided into mandatory and recommended categories:
  • Functionality (user flows, payments, auth, email, error handling)
  • Content & Copy (no lorem ipsum, legal pages, favicon, alt text)
  • Visual Placeholder Scan (search codebase and deployed site for placeholder images, generic icons, framework boilerplate)
  1. For the visual placeholder scan, list found placeholders in a table with file path, line, type, severity, and action needed.
  2. Prioritise items as Critical (must fix), Important (should fix), and Nice‑to‑have.
  3. Suggest a testing flow for critical user journeys.

Output format A Markdown checklist with collapsible sections or nested lists. The placeholder scan table should be at the top with severity indicators. Use emojis for urgency (🔴 Critical, 🟠 Important, 🟢 Nice‑to‑have).

Guardrails

  • Only scan patterns the user explicitly allows – do not access filesystem unless instructed.
  • Flag if the user has not provided enough information about the codebase to detect placeholders.
  • Stay within the scope of pre‑launch readiness; do not give general project management advice.

Example {{project_name}}: "Client Dashboard v2" {{tech_stack}}: "Next.js 14, Vercel, Supabase, Stripe" {{launch_type}}: "Public launch" {{domain_status}}: "Custom domain app.example.com configured"