Category

Planning AI Agent Loops

Planning loops that turn vague goals into scoped implementation plans and acceptance criteria. Every page is server-rendered, source-aware, and includes a copy-ready Markdown protocol.

All categories · 3 loops

All Planning loops

Planningmanual trigger Hardened

Launch Checklist Loop

Run a structured launch review covering build, SEO, policy pages, analytics, sitemap, and deployment verification.

CursorClaude CodeCodex

launchchecklistseodeploy

Kickoff preview

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.

Planningmanual trigger Hardened

Codex Project Context Loop

Build a clear Codex task goal from project files, constraints, done criteria, and stop conditions.

Codex

codexgoalplanning

Kickoff preview

Inspect the project context and write a strict, audit-friendly implementation objective with scope, constraints, done criteria, verification, and stop-if rules.
Goal: Create an audit-friendly agent objective before implementation.
Check command: find . -maxdepth 2 -type f | sort | head -100
Exit condition: The goal is concrete enough for an agent to execute and for a reviewer to audit.
Max iterations: 2
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 write a goal that allows vague completion or unverified claims.

Planningmanual trigger Hardened

Landing Page CRO Review

Review a landing page for message clarity, CTA focus, trust signals, mobile UX, and SEO alignment.

CursorClaude CodeCodex

landing-pagecrogrowth

Kickoff preview

Review the landing page for positioning, CTA focus, trust, mobile UX, and SEO alignment. Return prioritized fixes and avoid fake proof.
Goal: Improve landing page clarity and conversion without harming SEO.
Check command: curl -sL $URL | head -120
Exit condition: The page has clear positioning, primary CTA, trust signals, and SEO metadata.
Max iterations: 3
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 add fake testimonials, fake metrics, or misleading claims.

Why this category matters

Planning loops are useful because AI agents need explicit feedback gates and exit criteria. A plain prompt may produce a first draft; a loop tells the agent how to verify progress, handle failures, and stop with evidence.