executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
launch-planPlan a product launch: pre-launch, hour-by-hour launch day, follow-up, owners, risks. "plan our product launch"
Independent GitHub snapshot · Automated classification · Original documentation governs
Build a comprehensive launch playbook that coordinates all marketing activities across three phases — pre-launch, launch, and post-launch — to maximize impact and sustain momentum.
This skill produces a launch playbook — it performs no external action itself, so it runs freely. The gate governs the handoff: before ANY step of this playbook is executed by a downstream execution skill (/digital-marketing-pro:launch-campaign, /digital-marketing-pro:launch-ad-campaign, /digital-marketing-pro:send-email-campaign, etc.), that skill presents its own Execution Summary and the user must type yes. Never proceed on ambiguous input, never auto-execute a playbook step, and never auto-retry a failed one.
The user must provide (or will be prompted for):
~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.A structured launch playbook containing: