Planningmanual triggermarkdown-export Hardened

Launch Checklist Loop

A final pre-launch loop for indie projects and free tools.

Use loop copies the kickoff prompt. Copy Markdown and Download loop include the complete Markdown page with context, source attribution, anchors, and guardrails. Cursor / Claude Code buttons prepare the shorter kickoff prompt only.

Run shape

Supported agents

CursorClaude CodeCodex

Goal

Avoid launching with broken routes, missing policy pages, bad metadata, or unverifiable deployment.

Feedback gate

pnpm build

Stop condition

Build, deployment, SEO basics, policy pages, and critical user paths pass review.

Do not weaken, skip, delete, or rewrite the validation command to force success.

Do not claim completion until the stated exit condition is actually satisfied.

If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.

Required context

Give the agent these inputs before it starts the loop. This keeps discovery bounded and prevents vague retries.

Launch domain.

Critical pages.

Analytics/ads policy.

Deployment platform.

Required tools

The loop assumes these commands or integrations are available. Missing tools should be reported as blockers, not ignored.

build command

deployment URL

sitemap URL

How to run

Two separate pieces: the kickoff prompt starts the loop, while the downloaded Markdown carries the complete reference page.

1. Copy or download

Use the kickoff for a fast agent run. Download the full Markdown when you need source, context, and attribution in one file.

2. Paste into the agent

Start a fresh agent session in the target repo and provide the requested project context if the loop asks for it.

3. Let it self-pace

The agent should act, check evidence, retry only when the gate fails, and stop at the stated exit condition.

manual triggerPlanning Step flow

Manual start

Run build

Check critical pages

Check SEO and policy

Give launch verdict

Feedback gate

Build, deployment, SEO basics, policy pages, and critical user paths pass review.

not done → return to next actiondone → exit condition met

Action checklist

The diagram shows the order. This checklist keeps only the action, command, and failure handling needed during a real pass.

1. Run build

Verify the production build.

pnpm build

2. Check critical pages

Open homepage, loops, detail, categories, agents, sitemap, robots, privacy, terms, contact.

3. Check SEO and policy

Verify metadata, canonical, sitemap, robots, About, Contact, Privacy, Terms.

4. Give launch verdict

Separate blockers from warnings and nice-to-haves.

Kickoff prompt

This is the text copied by Use loop. It is intentionally shorter than the Markdown export.

Run a launch readiness checklist: build, deployed critical pages, SEO metadata, sitemap, robots, policy pages, analytics/ads, and final blockers.
Goal: Avoid launching with broken routes, missing policy pages, bad metadata, or unverifiable deployment.
Check command: pnpm build
Exit condition: Build, deployment, SEO basics, policy pages, and critical user paths pass review.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not mark launch-ready with missing policy pages or broken critical routes.

Quality

91/100

Safety

93/100

Expected output

Launch readiness verdict with blockers, warnings, and passed checks.

Related loops

Browse all

DevOpsmanual trigger Hardened

Deploy Verification Loop

After deployment, check production URL, health routes, metadata, and key user paths before declaring release success.

Claude CodeCodexGemini CLIOpenCode

deploysmoke-testrelease

Kickoff preview

Verify the deployed URL, critical pages, sitemap, robots, and metadata. Fix or report exact failures before declaring the release successful.
Goal: Confirm the deployed site responds correctly and key pages are usable.
Check command: curl -I $DEPLOY_URL
Exit condition: Critical deployed pages return expected status and visible content/metadata.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not claim deployment success based only on build success. Verify the deployed URL.

View

SEOmanual trigger Hardened

AdSense Readiness Audit

Check whether a free content/tool site has enough original value, policy pages, navigation, and ad-safe layout for AdSense review.

CursorClaude CodeCodex

adsensemonetizationpolicy

Kickoff preview

Audit the site for AdSense readiness: content depth, policy pages, navigation, mobile UX, and ad-safe layout. Return blockers and fixes.
Goal: Make the site credible, useful, navigable, and ad-safe before AdSense review.
Check command: curl -I $SITE_URL
Exit condition: Core content, policy pages, navigation, and ad placement are ready for review.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not place ads next to copy/download/source buttons where users may click accidentally.

View

SEOmanual trigger Hardened

SEO Metadata Audit Loop

Audit title, description, canonical, Open Graph, headings, and indexability for SEO-critical pages.

CursorClaude CodeCodex

seometadatacanonicalssr

Kickoff preview

Audit SEO metadata from server-rendered HTML for the target pages. Verify title, description, canonical, H1, Open Graph, and indexability, then fix and re-check.
Goal: Ensure SEO-critical pages have unique, server-rendered metadata and indexable content.
Check command: curl -sL $URL | head -80
Exit condition: Each target page has unique title, description, canonical, visible H1, and no accidental noindex.
Max iterations: 5
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not rely only on client-rendered metadata for SEO-critical pages. Verify server HTML.

View

CImanual trigger Hardened

Ship PR Until Green

Implement a scoped change, open or update a pull request, inspect CI, and continue until all required PR checks pass.

CursorClaude CodeCodex

pull-requestcigithub-actionsverification

Kickoff preview

Take this branch to a green pull request. Implement the requested change, run local verification, open or update the PR, run `gh pr checks`, inspect failures, fix root causes, and repeat until every required check passes or you hit the iteration cap.
Goal: Open or update a pull request and stop only when all required PR checks are green.
Check command: gh pr checks
Exit condition: All required pull request checks are successful and the PR is ready for review or merge.
Max iterations: 10
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not disable required checks, edit loops to skip jobs, or remove tests to make CI green.
- Do not merge the PR unless the user explicitly asked for merge authority.

View