Menu
Use after a product launch to review results - structured analysis of metrics, what worked, what didn't, and concrete next actions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when executing an implementation plan with four or more independent tasks touching different files, via the experimental agent-teams flag — parallel implementer teammates plus continuous async reviewers. Higher token cost; requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Use when starting creative work — adding features, building components, adding functionality, modifying existing behavior, or any time the user describes a new idea or capability they want to build.
Use when adding, modifying, or removing database tables, columns, indexes, views, functions, or RLS policies — any schema change targeting a shared or production database
Use when facing two or more independent investigations or research tasks in the current session — debugging multiple unrelated failures, exploring different solution approaches, or running parallel reads. Not for executing implementation plans (use subagent-driven-development, agent-team-development, or tmux-parallel-development for those).
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
| name | launch-retrospective |
| description | Use after a product launch to review results - structured analysis of metrics, what worked, what didn't, and concrete next actions |
Structured review of what happened after launch. Produces honest analysis with concrete next actions, not vanity metrics.
Announce at start: "I'm using the launch-retrospective skill to review the launch."
Step 1: Context gathering
Step 2: Four areas (one at a time)
Metrics review
What worked
What didn't work
Lessons and next actions
Step 3: Write output
docs/marketing/launch-retrospective.mdStep 4: Handoff
globalcoder-marketing:market-research or globalcoder-marketing:positioning-strategy with learnings as input