القائمة
Use when planning a product launch - builds a phased timeline with channels, milestones, owners, and KPIs
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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-plan |
| description | Use when planning a product launch - builds a phased timeline with channels, milestones, owners, and KPIs |
Build a phased launch timeline with channels, milestones, and KPIs. The master coordination document for the entire go-to-market effort.
Announce at start: "I'm using the launch-plan skill to build the go-to-market timeline."
Step 1: Context gathering
Step 2: Scoping questions (one at a time)
Step 3: Build phased plan
Present each phase separately for validation:
Pre-launch (weeks/months before)
Launch week
Post-launch (weeks after)
For each action: owner (if team), channel, timeline, success metric.
Step 4: Write output
docs/marketing/launch-plan.mdStep 5: Handoff
globalcoder-marketing:content-strategy to flesh out content needsglobalcoder-workflow:writing-plans to break them into executable tasks."