# Launch plan Human Guide

## What This Is For
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. It gives the agent a clearer input/output frame for growth marketing: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Launch plan agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for launch plan.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Launch plan guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- **What is launching**: Product, feature, service, rebrand, or event
- **Launch date**: Target date or date range
- **Launch goals**: Signups, revenue, coverage, awareness targets
- **Target audience**: Primary and secondary audiences for the launch
- **Available channels**: Which channels are active and resourced
- **Budget**: Dedicated launch budget (if any)
- **Assets available**: What already exists (product pages, demos, press materials, creative)
- **Team**: Who is involved and their roles
- Define launch tier (Tier 1 major, Tier 2 moderate, Tier 3 minor) to calibrate effort
- **Pre-launch phase** (T-30 to T-1): Teaser content, audience building, press seeding, influencer outreach, email list warming, landing page, waitlist
- **Launch phase** (T-0 to T+3): Coordinated announcement across all channels, press release, email blast, social blitz, paid media activation, community engagement
- **Post-launch phase** (T+4 to T+30): Performance monitoring, user feedback collection, content follow-up, retargeting, optimization, case studies

## Decision Points And Nuance
The original skill emphasizes: Purpose, Execution gate (MANDATORY — cannot be skipped), Input Required, Process, Output, Agents Used, Supporting file: skills/context-engine/compliance-rules.md, Section 1: Geographic Privacy Laws, 1.1 EU/EEA — General Data Protection Regulation (GDPR), 1.1b EU/EEA — AI Act Article 50 (Generative AI Disclosure).

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- The user must provide (or will be prompted for):
- | **Penalty Range** | Up to EUR 20 million or 4% of global annual turnover, whichever is higher. Supervisory authorities may also issue warnings, bans on processing, and orders to erase data. |
- **Treat the carve-out as conditional, not a free pass.** "Human-reviewed" requires named accountability. Don't claim editorial responsibility unless a named editor is willing to be on the record.
- | **Consent Model** | Opt-out. No prior consent required to send commercial email. Recipients must be given a clear way to opt out, and opt-out requests must be honored within 10 business days. |
- | **Consent Model** | Opt-out for sale/sharing of personal information. Opt-in required for consumers under 16 (under 13 requires parental consent). "Sharing" includes cross-context behavioral advertising. |
- | **Consent Model** | Opt-in. Consent must be free, informed, and unambiguous for a specific purpose. Legitimate interest is available as an alternative basis but requires a Legitimate Interest Assessment (LIA). |
- | **Penalty Range** | Up to 2% of revenue in Brazil, capped at BRL 50 million (~USD 10 million) per violation. ANPD may also issue warnings, publicize violations, and block or delete data. |
- | **Email Rules** | Specified Electronic Mail Act: opt-in required for commercial email. Sender ID and unsubscribe required. APPI requires specifying the purpose of use at collection. |

## Copy-And-Paste Prompt
```text
Use the Launch plan human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the indranilbanerjee/digital-marketing-pro skill entry for `launch-plan`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# /digital-marketing-pro:launch-plan

## Purpose

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.

## Execution gate (MANDATORY — cannot be skipped)

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.

## Input Required

The user must provide (or will be prompted for):

- **What is launching**: Product, feature, service, rebrand, or event
- **Launch date**: Target date or date range
- **Launch goals**: Signups, revenue, coverage, awareness targets
- **Target audience**: Primary and secondary audiences for the launch
- **Available channels**: Which channels are active and resourced
- **Budget**: Dedicated launch budget (if any)
- **Assets available**: What already exists (product pages, demos, press materials, creative)
- **Team**: Who is involved and their roles

## Process

1. **Load brand context**: Read `~/.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.
2. Define launch tier (Tier 1 major, Tier 2 moderate, Tier 3 minor) to calibrate effort
3. **Pre-launch phase** (T-30 to T-1): Teaser content, audience building, press seeding, influencer outreach, email list warming, landing page, waitlist
4. **Launch phase** (T-0 to T+3): Coordinated announcement across all channels, press release, email blast, social blitz, paid media activation, community engagement
5. **Post-launch phase** (T+4 to T+30): Performance monitoring, user feedback collection, content follow-up, retargeting, optimization, case studies
6. Build detailed timeline with owners, deliverables, and deadlines per task
7. Define success metrics per phase and overall launch KPIs
8. Identify risks and build contingency plans

## Output

A structured launch playbook containing:

- Launch overview with tier classification and success criteria
- Pre-launch checklist with timeline, deliverables, and owners
- Launch day runbook with hour-by-hour coordination plan
- Post-launch optimization plan with feedback loops
- Channel-by-channel activation plan with specific tactics
- Content and asset requirements list
- Risk register with contingency actions
- KPI dashboard with targets per phase

## Agents Used

- **marketing-strategist** — Launch architecture, phasing, goal setting, channel coordination
- **content-creator** — Launch messaging, content assets, announcement copy
- **pr-outreach** — Media strategy, press materials, influencer seeding

---

## Supporting file: skills/context-engine/compliance-rules.md

# Compliance Rules Reference

This file is the canonical compliance ruleset for the Digital Marketing Pro plugin. All marketing modules MUST check outputs against these rules before delivery. Rules are structured for programmatic consumption by the context engine.

---

## Section 1: Geographic Privacy Laws

### 1.1 EU/EEA — General Data Protection Regulation (GDPR)

| Field | Detail |
|---|---|
| **Region** | European Union / European Economic Area (27 EU member states + Iceland, Liechtenstein, Norway) |
| **Law** | General Data Protection Regulation (GDPR) |
| **Year Enacted** | 2016 (enforced May 25, 2018) |
| **Consent Model** | Opt-in. Explicit, informed, freely given, specific, and unambiguous consent required before processing personal data. Consent must be as easy to withdraw as to give. Legitimate interest may apply in narrow B2B contexts but requires a documented balancing test. |
| **Email Rules** | Prior opt-in required for all marketing emails. Soft opt-in exception: existing customers may be emailed about similar products/services if given an easy opt-out at collection and in every message. Every email must include sender identity, physical address, and a functional unsubscribe mechanism honored within 30 days. |
| **Cookie/Tracking Rules** | Prior consent required for all non-essential cookies and trackers (ePrivacy Directive). Cookie banners must allow granular choice (accept/reject by category). Pre-ticked boxes are invalid. Analytics cookies require consent unless strictly necessary. Server-side tracking of personal data still requires a lawful basis. |
| **Penalty Range** | Up to EUR 20 million or 4% of global annual turnover, whichever is higher. Supervisory authorities may also issue warnings, bans on processing, and orders to erase data. |
| **Key Marketing Impact** | Double opt-in is industry standard. All lead forms need clear consent checkboxes (not bundled). Data Processing Agreements required with every martech vendor. Privacy policy must disclose all data recipients. Cross-border data transfers require adequacy decisions, SCCs, or BCRs. Right to erasure means suppression lists must be maintained. Profiling for ad targeting requires explicit consent or legitimate interest with opt-out. |

### 1.1b EU/EEA — AI Act Article 50 (Generative AI Disclosure)