← ClaudeAtlas

marketing-brieflisted

Use when the user wants to generate a marketing brief from a GitHub PR, git ref comparison, codebase feature, or freeform description of a feature or product change
AlemTuzlak/skills · ★ 39 · AI & Automation · score 68
Install: claude install-skill AlemTuzlak/skills
# Marketing Brief Generator Generate structured marketing briefs from code changes. Designed for non-marketers who need professional-quality briefs. ## Input Resolution Resolve the argument (if provided) in this order: 1. Matches GitHub URL or `#\d+` pattern → **PR** 2. Contains `...` or `..` → **git ref range** 3. Resolves to existing file/directory → **codebase feature** 4. Otherwise → **freeform text** If no argument is provided, ask: "What should I analyze? You can provide a PR URL/number, a git ref range (e.g. v1.0...v2.0), a file/directory path, or just describe the feature." If multiple interpretations match, confirm with the user. ## Process Flow ```dot digraph marketing_brief { rankdir=TB; "Resolve input" [shape=box]; "Phase 1: Discovery" [shape=box]; "Understanding confirmed?" [shape=diamond]; "Sensitive items?" [shape=diamond]; "Get framing approval" [shape=box]; "Phase 2: Configure" [shape=box]; "Phase 3: Generate" [shape=box]; "Phase 4: Output" [shape=box]; "Resolve input" -> "Phase 1: Discovery"; "Phase 1: Discovery" -> "Understanding confirmed?"; "Understanding confirmed?" -> "Phase 1: Discovery" [label="no, revise"]; "Understanding confirmed?" -> "Sensitive items?" [label="yes"]; "Sensitive items?" -> "Get framing approval" [label="yes"]; "Sensitive items?" -> "Phase 2: Configure" [label="no"]; "Get framing approval" -> "Phase 2: Configure"; "Phase 2: Configure" -> "Phase 3: Generate"