tech-to-marketing-brief

Tech-to-Marketing-Brief (Product & R&D-side promotional material generator)

When product and R&D personnel (technical/algorithm) need to deliver new features to the operations team, or need to package cold technical metrics into a promotional plan with "human touch" and "internet sensibility," this skill must be triggered.

Skill Background

Product and R&D personnel (technical, algorithm) are often good at describing "how it is implemented" and "technical metrics," but what the operations team needs is "what pain point it solves" and "how to spark dissemination." The role of this skill is to act as atranslator and master planner, transforming fragmented technical descriptions, through divergent thinking, pain point association, and style reshaping, into three core deliverables that can be directly handed to the operations and development sides.

Workflow

When the user inputs scattered descriptions of technical features, strictly follow the steps below:

Step 0: Expert Retrieval (recommended)

Before formally starting, in order to obtain more professional industry perspectives and standard templates, it is recommended to use /skill::plugin-search-and-use to retrieve expert plugins in the following fields (located under the knowledge-work-plugins directory):

• Marketing field: Retrieve campaign-plan (event planning),content-creation (content creation),brand-review (brand tone check), and other plugins to assist with Step 2 and Step 3.
• Product management field: Retrieve the write-spec (requirements writing) plugin to improve the professionalism of writing the Jira Ticket in Step 4.
• Context acquisition: If benchmarking against competitors is needed, retrieve competitive-brief (competitor brief) plugin.

Step 1: Divergent Thinking & Research

• Extract core technical points: Identify the technical highlights in the user input (such as long-text processing, complex logical reasoning, cross-modal understanding capabilities).
• Pain point translation: Translate technical metrics into specific limitations or efficiency bottlenecks in actual production environments. For example: map "ultra-long context" to "breaking the information fragmentation during multi-document correlation analysis"; map "CoT reasoning" to "solving edge cases that are easily overlooked in decision chains."
• (Optional) Web search: Use the WebSearch tool to search for recent common complaints or hot vertical-domain topics among the target user group (such as developers, copywriters, finance personnel), looking for real pain points that can be incorporated.

Step 2: Write the Operations Brief document (The Operations Brief)

Generate a standard Brief document that can be directly delivered to operations or external bloggers. It must include the following modules:

1. Differentiated perception (core mindset): Clarify the core change brought by the technology (such as: the cognitive leap from "AI as a tool" to "AI as a deep business participant").
2. High-fidelity test scenarios (core): Aimless, low-intensity generalized tests (such as simple polishing/summarization) are strictly prohibited. 1-2 vertical test scenarios from the real world with extremely high information density and highly complex logic should be designed (such as: long-chain alignment of multi-source fragmented information, automation of non-standard processes in specific professions).
3. Conversion and operation path: Explain the product's onboarding entry points, specific model versions, and how features are toggled.
4. Review Red Lines: Purely "praise-style" reviews are prohibited. It must require showing the model's "real exploration process" in solving problems or its "evolution path from chaos to order."

Step 3: Produce a Social Media Case Library (Social Media Cases)

Based on the above scenarios, provide case prototypes for different audience groups:

1. Visual/Sensory-Driven Type (e.g., Xiaohongshu)：
   • Style: Problem-first, strong logical contrast, emphasis on "certainty."
   • Content: Focus on using Before & After comparisons to show how originally extremely time-consuming and cumbersome work becomes lightweight and transparent.
2. Deep-Insight Type (e.g., WeChat Official Accounts)：
   • Style: Professionalism, no buzzwords, no jargon.
   • Content: Analyze from underlying logic how technological breakthroughs reshape business processes, and present non-consensus insights into the vertical industry.
3. Minimal-Fact Type (e.g., X / Moments)：
   • Style: Hook + hardcore evidence.
   • Content: A highly impactful factual statement + accompanying output screenshots that reflect depth of logic.

Step 4: Break Down the Supporting Development Tasks (Jira Tickets)

To support the above marketing activities, the product needs to have the corresponding implementation and delivery capabilities. Please output 1-3 specific Jira tasks (Epic/Task):

• Title: Format such as [Feature] 配合XX宣发：增加XXX功能
• User Story：As a... I want to... So that...
• Acceptance Criteria (AC): For example: the gateway layer needs to identify external requests and automatically inject an optimized system instruction set; or launch a dedicated business scenario template in the product backend.

Style Guidelines (Tone & Guidelines)

• Reject formulaic expressions: The output must match the perspective of a senior business expert. It is strictly forbidden to use filler such as "As the AI era arrives," "essentially," or "is committed to."
• Create differentiated tension: Establish tension by uncovering "counterintuitive facts" or "hidden contradictions in the business chain."
• Details determine granularity: All cases and scenarios must come from real, specific business slices (such as a specific operation flow for a specific profession, or emergency tasks under extreme pressure). Overly vague and generic descriptions are strictly prohibited.

References & Expert Resources (References & Expert Resources)

When executing this skill, please combine the following resources:

1. Built-in reference documents：

   • Operations Brief Planning Reference: marketing_campaign_planning.md (Explains in detail how to translate technical selling points into business selling points).
   • Social Media Brand and Tone Reference: social_media_brand_voice.md (Defines the writing style for Xiaohongshu, WeChat, and X).
   • R&D Implementation Plan Reference: jira_agile_spec.md (Provides standard specifications for writing User Stories and AC).

2. External expert plugins：

   • Use /skill::plugin-search-and-use to retrieve knowledge-work-plugins/marketing sub-plugins under it to obtain the latest market insights and templates.
   • Use /skill::plugin-search-and-use to retrieve knowledge-work-plugins/product-management plugins under it to optimize the granularity of Jira tasks.