qishuo-ai/pr-pitch-skill

PR Pitch Skill

Purpose

PR Pitch Skill is a standalone Agent Skill for strategy-first PR proposal development.

It helps PR, communications, brand and marketing professionals turn a brief into:

• communication problem diagnosis;
• insight;
• strategy;
• core proposition;
• campaign architecture;
• content, media and PR plan;
• pitch storyline;
• page plan;
• style direction;
• deck QA.

This skill follows the Qishuo PR Pitch Methodology.

Core rule:

Brief -> Diagnosis -> Insight -> Strategy -> Proposition -> Campaign -> Storyline -> Page Plan -> Deck

Do not move directly from a raw brief into PowerPoint production unless the user explicitly says:

跳过策略，直接排版现有内容

or an equivalent instruction that the strategy and content are already approved.

When to Use

Use this skill when the user asks for:

• PR proposal development;
• communications strategy;
• brand campaign planning;
• product or service launch proposals;
• annual retainer pitches;
• media strategy;
• integrated marketing proposals;
• overseas PR proposals;
• automotive PR pitches;
• pitch deck structure;
• page planning;
• proposal QA.

Trigger commands include:

• Use PR Pitch Skill for this brief.
• 使用 PR Pitch Skill 处理这个 Brief。
• Start PR Pitch
• Run Qishuo Method
• 开始提案
• 进入 Qishuo 提案流程

Inputs

The only required input is:

• Brief

Optional inputs:

• Brand
• Market
• Category
• Budget
• Timeline
• Deliverables
• Existing Research
• Reference Deck
• Style Preference

If optional fields are missing, do not block. Proceed with the brief, state assumptions, and list critical unknowns that affect strategy.

Supporting Files

When available, use:

• START.md for startup behavior;
• AGENTS.md for project-level rules;
• runtime/project_state_template.md for multi-step projects;
• workflows/00_intake.md for structured brief parsing;
• workflows/gates.md for Proposal Gates;
• workflows/style_router.md for style-system selection;
• style-systems/STYLE_SYSTEM_SPEC.md for style-system structure;
• style-systems/automotive/ for automotive proposals;
• visual-engine/ for layout retrieval, matching, geometry, content fit and visual QA;
• layout-library/index.json for public demo layout retrieval;
• templates/start_prompt.md for reusable prompt examples;
• templates/layout_retrieval_report_template.md for PPT production reporting;
• tests/ for self-test behavior.

Workflow

Phase 0 - Intake

Understand what the user provided and what they expect.

Use workflows/00_intake.md.

Output:

• input type;
• project category;
• expected deliverables;
• brief quality score;
• critical unknowns;
• recommended next phase.

Phase 1 - Brief Diagnosis

Separate business and communication issues.

Output:

• Business Objective
• Communication Objective
• Business Problem
• Communication Problem
• Audience
• Product / Brand Truth
• Market Context
• Competitors
• Constraints
• Gate 1 - Brief Gate

Phase 2 - Research Questions

Identify what must be checked before confident strategy.

Output:

• required research questions;
• assumptions that can be used for first-round thinking;
• facts that must not be invented;
• external validation needs.

Phase 3 - Insight

Develop a strategic insight, not just an observation.

Output:

• key observation;
• tension;
• so what;
• strategic opportunity;
• Gate 2 - Insight Gate.

Phase 4 - Strategy

Define what the proposal recommends doing and why.

Output:

• strategic conclusion;
• one-sentence strategy;
• strategic pillars;
• reasons to believe;
• implications for campaign and content;
• Gate 3 - Strategy Gate.

Phase 5 - Proposition

Create the central communication expression.

Output:

• core proposition;
• campaign theme or Big Idea if useful;
• narrative system;
• why the proposition follows from strategy;
• Gate 4 - Proposition Gate.

Phase 6 - Campaign Architecture

Turn strategy into an actionable campaign system.

Output:

• campaign role;
• stages;
• hero moments;
• content pillars;
• PR mechanisms;
• owned / earned / paid / shared roles;
• audience journey;
• Gate 5 - Campaign Gate.

Phase 7 - Content / Media / PR

Define how the campaign becomes communication work.

Output:

• content matrix;
• media strategy;
• KOL / KOC role if relevant;
• event or launch role if relevant;
• channel tasks;
• deliverables by workstream.

Phase 8 - Timeline / KPI

Define timing and measurement without fabricating outcomes.

Output:

• phase timeline;
• key milestones;
• controllable deliverables;
• measurable outcomes;
• KPI groups;
• dependencies and risks.

Phase 9 - Pitch Storyline

Turn the strategy into a persuasive deck argument.

Output:

• pitch logic;
• section structure;
• why each section exists;
• meeting flow;
• Gate 6 - Pitch Gate.

Phase 10 - Page Plan

Plan pages before slide production.

Output each page with:

• page number;
• page title;
• strategic purpose;
• key message;
• proof or content;
• page type;
• visual direction;
• transition from previous page.

Phase 11 - Style System

Select the available style system using workflows/style_router.md.

Current public style systems:

• style-systems/automotive/

If no style system matches, use:

• generic-strategy-first

Do not pretend unavailable style systems exist.

Output:

• selected style system;
• reason;
• files used;
• visual direction;
• forbidden styles.

Phase 12 - Layout Retrieval / PPT Production

Do not start from a blank slide when a layout candidate exists.

Use:

• visual-engine/retrieval.md
• visual-engine/matching.md
• visual-engine/geometry.md
• visual-engine/content_fit.md
• visual-engine/production.md
• layout-library/index.json

Required sequence:

Page Intent -> Page Type -> Layout Retrieval -> Layout Match -> Geometry Extraction -> Content Adaptation -> Render -> Visual QA

Output:

• top 3 layout candidates;
• selected Primary Layout ID;
• Backup Layout ID;
• content fit status;
• adaptations made;
• reference fidelity score if a reference layout is used;
• layout_retrieval_report.md.

Free design is allowed only when no public, private or generic layout can support the page intent and the report explicitly explains why.

Phase 13 - Deck QA

Run QA before final delivery.

Output:

• strategy QA;
• PR logic QA;
• narrative QA;
• evidence QA;
• visual QA;
• reference fidelity QA when a reference layout is used;
• confidentiality QA;
• final decision: Ready / Needs revision / Not ready.

Output Contract

When the user provides a brief and asks for a first-round proposal structure, output:

1. Intake Summary
2. Brief Diagnosis
3. Critical Unknowns
4. Insight
5. One-sentence Strategy
6. Core Proposition
7. Campaign Architecture
8. Pitch Storyline
9. Page Plan
10. Selected Style System
11. Proposal Gates
12. QA Risks

When the user asks for page planning, each page must include:

• page number;
• page title;
• strategic purpose;
• key message;
• proof or content;
• page type;
• visual direction;
• transition.

When the user asks for deck production, first confirm that:

• strategy is defined;
• proposition is defined;
• campaign architecture is defined;
• page plan is approved or at least accepted as a working draft;
• style system or visual direction is selected.
• layout retrieval has returned concrete Layout IDs, unless retrieval failed and free design is explicitly justified as a last resort.

When producing a PPT or slide sample, each page must record:

• page intent;
• page type;
• candidate layout IDs;
• selected layout ID;
• content fit status;
• geometry source;
• render output;
• reference fidelity;
• visual QA result.

Stop Conditions

Ask the user before continuing when:

• the brief is too vague to identify a communication problem;
• the user asks for claims that require external facts but no source is available;
• budget, legal, compliance or approval constraints materially affect the recommendation;
• the user asks to include real client confidential material in a public example;
• the user asks for fake media coverage, fake logos, fake awards or fabricated evidence;
• the user asks for final PPTX production before strategy and page plan are clear, and has not explicitly asked to skip strategy.
• no layout can support the page intent and free design would materially change the approved page plan.

Do Not Do

• Do not produce PowerPoint immediately after a raw brief.
• Do not fabricate data.
• Do not create fake media coverage.
• Do not invent client facts.
• Do not treat a creative idea as strategy.
• Do not use templated marketing jargon to hide weak thinking.
• Do not repeat content just to fill pages.
• Do not promise uncontrollable outcomes.
• Do not use confidential client material in public examples.
• Do not claim unavailable style systems exist.
• Do not build slides from blank pages when a matching layout exists.
• Do not describe a layout vaguely when a concrete Layout ID can be retrieved.
• Do not expand content until it destroys the selected layout.

Confidentiality Rules

• Do not reveal private client information.
• Do not include credentials, tokens, private paths or personal information.
• If the user provides confidential material, use it only for the current task and do not turn it into public examples.
• Fictional examples must be clearly labeled as fictional.