Three hands-on: 3 prompts end to end

Run Prompt A / B / C on a real event case end to end — each with full text, how-to-modify, and how-to-verify; plus the three real artifacts to inspect.

What This Lesson Is

Lesson 1 gave the "why" and the map. This lesson gives "how to do it."

We use a real event case ("Feifan Zhichuang · Future Partner AI Roadshow Day") to run the three prompts A / B / C end to end:

Hands-on 1 | Prompt A — Requirement clarification: turn a one-line ask into a structured Brief
Hands-on 2 | Prompt B — Plan design: 3 directions + evaluation + complete plan
Hands-on 3 | Prompt C — Execution plan: timeline / WBS / Run of Show / budget / materials / risks / pre-event checklist

Each prompt has 4 sections: when to use → full prompt text → how to modify → how to verify. Copy first, use second, modify third.

活动策划师 has been uploaded to the SkillHub store. It scripts the three-step flow of the prompts below — once installed, the next time you say "I want to run a client appreciation event next month," the Agent will automatically run A → B → C end to end.

Copy the prompt below to any SkillHub-compatible Agent to install automatically:

First check whether SkillHub is installed. If not, follow https://skillhub.cn/install/skillhub.md to install SkillHub (CLI only), then install the [活动策划师](https://skillhub.cn/skills/user_4fc8972a/ai-event-planner) skill. If already installed, directly install the [活动策划师](https://skillhub.cn/skills/user_4fc8972a/ai-event-planner) skill.

Once installed, use the prompt below to let the Agent first understand the Skill, then execute it step by step:

Read this file — it is a skill. Analyze what steps it contains, what the standard is for each step, and how I should work with you.

New to SkillHub? No worries — the three full prompts below can be copy-pasted into any AI tool directly. The Skill is just a "productivity pack" that automates the three-step flow, not a requirement.

Case Background (Runs Through All 3 Steps)

To make the outputs comparable, here's the input:

Raw need (Prompt A's input):

Next month the company wants to host a 100-person offline AI-themed sharing event, hoping to lift brand visibility and pick up some leads.

Confirmed Brief highlights (Prompt A's output → Prompt B's input):

Event type: offline industry-sharing conference + VIP dinner
Scale: 100 main venue + 20–30 VIP dinner
Budget: ≤ 50K (hard cap)
Core goal: 30–50 qualified leads
Audience: founders, owners, managers across industries (mixed)
Key constraints: ~1 month to event, tight budget, mixed background (can't be too technical or too shallow)

The three attachments (inspected below) are the real outputs of this event — sanitized for reference:

AI活动策划Brief.md — Prompt A output
AI活动策划方案.md — Prompt B output
AI活动执行计划.md — Prompt C output

Hands-on 1 | Prompt A: turn a vague need into a professional Event Brief

What you'll learn on this page

Use AI to ask all the key questions in one pass (goals, audience, content, time, budget, format, resources, metrics)
Quickly sort requirements and constraints (avoid omissions, avoid back-and-forth, avoid late-stage reversals)
Output a clear Event Brief as the basis for the next step (with evidence, you can produce quality plans efficiently)

When to use

The boss / client / yourself drops a one-liner like "help me organize an event" or "next month we need an investment event"
Information is severely lacking; if you just hand it to AI for a plan, AI will fill in the blanks itself
You need an Event Brief that can flow through the team and be understood by everyone

Core moves (4 steps)

1. Assign a role     →  You are a senior event planning consultant
2. Don't plan yet    →  Don't write the event plan directly yet
3. Check info first  →  Verify goals, audience, time, location, budget, resources
4. Ask then output   →  3–5 key questions per round; once info is confirmed, generate the Event Brief

Full prompt

# Role

You are a senior event planning consultant with 10+ years of experience, specializing in corporate events, brand events, client events, industry conferences, training events, and offline salons.

Your task is NOT to immediately write me an event plan. Your task is to help me clarify the event requirements first.

# My Raw Need

【Paste the original event request from your boss, client, or yourself here】

Example:
Next month the company wants to host a 100-person offline AI-themed sharing event, hoping to lift brand visibility and pick up some leads.

# Your Task

First analyze my requirements.
Do not output a complete event plan yet.
Assess whether the current information is enough to plan the event, and find every important piece of missing information that could affect the plan's quality.

Focus on these dimensions:
1. Event goals
2. Target audience
3. Event scale
4. Time
5. City and venue
6. Budget
7. Existing company resources
8. Guest resources
9. Promotion channels
10. Desired business outcomes
11. Event format
12. Other constraints

# Step 1: Information Diagnosis

Output first:
| Information dimension | Currently known | Clear? | What still needs confirming |

Only list information that truly affects the event plan.

# Step 2: Ask Me Questions

Based on your assessment, ask me only the 3–5 most important questions per round.

Questions must:
1. Be understandable by a layperson
2. Offer choices where possible
3. Not ask 10+ questions at once
4. Prioritize information that will directly change the plan
5. Not repeat information already clear

After I answer, keep assessing whether to ask more.
Stop asking once you have enough information.

# Step 3: Generate the Event Brief

Once information is confirmed, organize it into an "Event Planning Brief":
## 1. Event basics
Event name:
Event type:
Event time:
Event location:
Event scale:

## 2. Event background
In ≤100 words, summarize why this event is being held.

## 3. Core goals
Distinguish:
Core goals:
Secondary goals:
Be specific — avoid empty phrases like "boost visibility".

## 4. Target audience
Core audience:
Audience profile:
Why they would attend:

## 5. Core event needs
List 3–5 items.

## 6. Budget and resources
Budget range:
Existing resources:
Resources to be acquired:

## 7. Constraints
Time, budget, venue, people, brand, etc.

## 8. Success metrics
Propose 5–8 measurable indicators. e.g. signups, attendees, attendance rate, qualified leads, engagement, social reach, satisfaction.

## 9. Items still to confirm
If any information is uncertain, list separately.

# Constraints

Do not make up facts I haven't provided.
Mark uncertain info explicitly as 【to be confirmed】.
Point out any obviously unreasonable or conflicting requirements.
Use professional but easy-to-understand language.

How to modify

What to change	How to change
Only one specific scenario (e.g. investment event / client appreciation / training)	In "Role", add: "This round focuses only on XX-type events"
Some info is already known (e.g. time and location are set)	In "My Raw Need", write confirmed info clearly to skip corresponding questions
Don't want to be asked too many questions	Change "ask only the 3–5 most important questions" to "ask only the 3 most critical"
Want a Brief without back-and-forth	In "Constraints", add: "If I mark 【use reasonable inference】, please infer and label 【to be confirmed】"

How to verify

After running once, check against this list:

Output an information diagnosis table (not a direct plan)
Questions capped at 3–5 per round, not 10+ at once
Multi-dimensional diagnosis, not just budget / time
Final Brief covers the full 一–九 structure
Uncertain items are marked 【to be confirmed】, no "I'll fill that in for you" inventions
Conflicts are actively flagged (e.g. 50K budget × full-day + VIP dinner × 100 people)

Pass standard: the Brief can be sent directly to a colleague / boss without re-explaining.

Real-output walkthrough (Attachment 1 | AI活动策划Brief.md)

The Brief that came out (key items):

Event type: 100-person offline AI-themed sharing
Core goals: lift brand awareness; acquire leads
Target audience: local SMB owners, managers, marketing/ops leaders
Event time: Saturday afternoon
Event budget: ≤ 30K
Existing resources: AI guest speakers, public WeChat, enterprise WeChat, private community
Key metrics: 100 signups ｜ 70 attendees ｜ 30 qualified leads

Key design choices:

Clarify first, then plan — AI didn't make up any key parameters
Budget 30K, tighter than the original "≤ 50K" — because AI asked "3K and 5K plans are very different, which one?"
70% attendance rate as a key metric — set after AI asked "what's your typical signup-to-attendance ratio?"
【to be confirmed】 kept on 5 items to avoid losing the basis during execution

Remember: a good start is half the battle! Clarify first, then think it through, then break it down.

Hands-on 2 | Prompt B: brainstorm → compare → deepen into a complete plan

What you'll learn on this page

6 directions to let AI "think it through" (participant experience / content & flow / promotion / venue / risk / budget)
Generate 3 different plans in one go, compare, pick the best
"AI recommends + human decides" 4-step decision method
Form a complete event plan ready to hand to the execution team

When to use

Already have a confirmed Event Brief
Want to see 3 different directions, not just AI's default
Need a complete plan that can move into execution

Full prompt

# Role

You are a senior brand event planning director, with experience in marketing, user ops, content, and offline event execution.

Your task is to design a truly attractive, viral, and executable event for me, based on the Brief below.

# Event Brief

【Paste the final Event Brief from Hands-on 1】

# Stage 1: Don't write a full plan yet

First propose 3 distinctly different event planning directions.

Don't just rename things.
The 3 plans should differ clearly in core idea, event format, interaction model, or viral logic.

Output as:
| Plan | Theme | One-line idea | Core play | Highlight | Why it fits | Potential issues |

# Stage 2: Plan evaluation

Score the 3 plans on these dimensions, 0–10 each:
1. Fit to event goals
2. Appeal to target audience
3. Creativity
4. Virality
5. Interactivity
6. Business conversion potential
7. Execution difficulty
8. Cost control
9. Risk level

Output:
| Dimension | Plan A | Plan B | Plan C |
|---|---:|---:|---:|

Note:
For execution difficulty and risk, clarify whether "higher score = easier" or "higher score = riskier" to avoid ambiguity.

Finally give:
Recommended plan:
Why:
Highlights to absorb from the other two:

# Stage 3: Generate the complete plan

Based on the recommended plan and absorbing worth-keeping parts from the others, output a complete event plan:

# 《XXXX Event Plan》
## 1. Event background
Why this event. ≤200 words.

## 2. Event goals
Brand goals
User goals
Business goals
Quantify each.

## 3. Event theme
Main title:
Subtitle:
Slogan:
Core idea:

## 4. Target audience
Core users:
User profile:
Core needs:
Reasons to attend:

## 5. Event basics
Time:
Location:
Scale:
Format:
Duration:

## 6. Overall event design
A paragraph explaining the core logic of the whole event.

## 7. Event highlights
3–5 truly perceivable highlights. Avoid empty phrases like "rich content", "varied formats", "full of insights".

## 8. Run of show
First, the high-level flow.
| Time | Segment | Content | Purpose |

## 9. Key segment design
Expand the 3–5 most important segments:
Segment name:
Play:
Participation:
Required resources:
Expected effect:

## 10. Guest and content design
What kinds of guests are needed.
Do not fabricate real people.
Explain what content role each type of guest plays.

## 11. User interaction design
Consider separately:
Before check-in
During the event
After the event
How to lift participant engagement.

## 12. Promotion plan
Across:
Pre-launch
Sign-up period
Final sprint
Event day
Post-event

## 13. Sign-up and conversion design
If the event has lead or conversion goals, design a natural path. Focus on:
Why users leave contact info.
Why they would inquire further.
How to follow up after the event.
Avoid hard selling.

## 14. Effectiveness evaluation
Key post-event metrics.

## 15. Plan risk check
Stand in three roles to check the plan once:
Client lead
Execution lead
Ordinary attendee
Each lists their top 3 likely questions.

# Constraints

1. All content must match the Brief.
2. Do not exceed the budget.
3. Mark uncertain info 【to be confirmed】.
4. Do not fabricate venue quotes, guest prices, policy requirements.
5. All ideas must consider real execution difficulty.
6. Few empty slogans, many concrete actions.
7. Output must be understandable by ordinary executors.

6 directions to let AI "think it through"

#	Direction	Focus
01	Participant experience	The full journey from entry to exit; which segments wow, which lose them; how to lift satisfaction and interaction
02	Content & flow details	Whether each segment's content is reasonable; whether time allocation is right; whether transitions are smooth
03	Virality & influence	How to design viral highlights and topics; social path and diffusion design; how to extend the event's influence cycle
04	Venue & atmosphere	Whether the venue is comfortable and accommodating; lighting / audio / stage design; on-site decor and detail optimization
05	Risk & contingency	What risks could appear; the contingency system and owners; how to lower the chance of mistakes
06	Budget & resource optimization	Whether the budget allocation is reasonable; what can be swapped or optimized; how to achieve goals at lower cost

AI tip: thinking it through is about empathy + breaking down details + predicting risks — AI helps you find the blind spots you didn't think of.

Generate 3 different plans in one go

Why generate multiple plans? — broaden ideas + compare trade-offs + reduce bias + faster decisions.

Real case: after running 3 directions, AI returned:

Dimension	Plan A — Solid & Steady	Plan B — Interactive	Plan C — Light & Viral
Positioning	Professional content & deep experience	Strengthen participation and immersion	Lightweight, viral, low-barrier participation
Core highlight	Insight + deep interaction	Strong interaction + scene-based experience	Lightweight content + viral spread
Format	Keynote + roundtable + workshop	Interactive game + experience zone + check-in tasks	Online live + community interaction + giveaway
Best for	Industry forum, professional summit	Brand event, user carnival	Online event, brand promotion
Strengths	Deep content; long-term professional influence	Lively atmosphere; viral; fits younger audience	Wide reach; cost-controlled; flexible
Possible challenges	Long prep; traditional format	High execution detail; large venue & staff	Limited interaction depth; weaker stickiness

Remember: there is no best plan, only the most fitting. AI gives you choices, you make the call.

AI provides information, plans, and suggestions, but can't take responsibility for you. Combine goals, resources, and risks to make the most fitting choice.

Four-step decision method:

Align goals — which plan best achieves the event goals?
Assess resources — can the team, budget, time, and venue support it?
Compare risks — what are the risk points? What's the backup?
Decide — make the choice, clarify execution and ownership!

Caution: don't over-rely on AI

AI has no situational awareness: it can't predict sudden on-site changes
AI has no values: it can't judge long-term brand–user relationships for you
AI doesn't bear responsibility: the final result, good or bad, is on the decision-maker

AI is your advisor, not your boss. You decide, you own the outcome, you take the credit!

How to modify

What to change	How to change
Want more directions (4 or 5)	In "Stage 1", change "3" to "4" or "5"
Don't want 9-dimension evaluation	In "Stage 2", drop unnecessary dimensions, keep 3–5 most important
Already have a direction in mind	At the top, add: "After listing 3 directions, focus on deepening Plan X"
Very tight budget	In "Constraints", add: "Any budget item over 20% of total budget must be marked 【to be confirmed】"
Want a shorter plan	In "Constraints", add: "Keep the plan under 5000 words; key segments ≤4"

How to verify

Stage 1 outputs 3 clearly different directions, not "three similar names"
Stage 2 scores 9 dimensions and clarifies the "score direction"
Recommended plan + reason + highlights to absorb from others is given
Stage 3 plan covers the full 一–十五 structure
Highlights avoid empty phrases ("rich content", etc.)
Risk check covers client / execution / attendee perspectives

Pass standard: the plan can be handed directly to the execution team to start prep, no need to ask "so what do we do".

Real-output walkthrough (Attachment 2 | AI活动策划方案.md)

The plan that came out (key items):

#1 Event goals: strengthen community engagement and member interaction; lift participation and belonging; add 200+ valid users; boost content interaction 30% during the event; accumulate quality content for later conversion
#2 Core idea: "Community Energy Station" — check in together, grow together, shine together; theme = check-in tasks + topic interaction + energy ranking + lucky draw & sharing
#5 Key flow: warm-up (3 days) → ignition (7 days) → climax (3 days) → wrap-up (2 days)
#10 Plan outline: background & goals / theme / target users / core idea / run of show / interaction design / promotion / commercial conversion / budget / metrics (10 modules)

Key design choices:

Clear goals: direction doesn't drift
Creativity solidified: highlights stand out
Executable plan: ready to land
AI drafts first, human judges and optimizes

Remember: the more thoroughly you think it through, the smoother the execution, the better the result. 10 minutes of thinking saves 10x the time and cost later.

Hands-on 3 | Prompt C: turn the plan into an executable project plan

What you'll learn on this page

Six execution questions to break the plan into a landing-ready execution plan
4 key tables: event timeline / task assignments / resource requirements / budget breakdown
Run of Show deep-dive: keep the on-site calm, in order, and engaged
A work plan that ordinary executors can use directly

When to use

Already have a finalized event plan
Entering prep period, going from "plan" to "project plan"
You want AI as a "project manager" not a "planning director"

Six execution questions

The plan answers "what"; the execution plan answers "how".

1. Who does it?       →  Clear people and roles
2. When?              →  Reverse-engineer timeline and milestones
3. How much money?    →  Budget framework and cost control
4. What to prepare?   →  Materials, venue, equipment, guests
5. How to run it?     →  Run of Show and on-site rhythm
6. What if it goes wrong? →  Risk and contingency plans

Full prompt

# Role

You are an event project manager with rich offline event execution experience.
You are taking over a finalized event plan.
Your goal is NOT to keep generating ideas, but to break the plan into a truly executable, checkable, pushable project plan.

# Event Plan

【Paste the final plan from Hands-on 2】

# Current requirement

Do an execution feasibility check on the plan, then complete the following.

---

# Part 1: Execution Feasibility Check

Check the plan for these issues:
1. Missing information
2. Time conflicts
3. Resource shortfalls
4. Budget risks
5. Staffing risks
6. Venue risks
7. Equipment risks
8. Guest risks
9. User experience risks
10. Safety risks

Output:
| Issue | Severity | Why it's an issue | Suggested fix |

Severity: High / Medium / Low
Mark unknown info as 【to be confirmed】.

---

# Part 2: Event Prep Timeline

Take the event day as T.
Count backward from T-30.
Include at least: T-30 / T-21 / T-14 / T-7 / T-3 / T-1 / T / T+1 / T+3 / T+7

Output:
| Milestone | Core goal | Specific task | Output | Owner role |

Tasks must be concrete enough to execute.
Not "do promotion" — instead "finish the first round of posters, sign-up page, and WeChat Moments copy, then start the first round of channel posting."

---

# Part 3: WBS Breakdown

Break the event down into concrete tasks. At minimum cover:
Project lead / Venue / Guests / Content / Design / Promotion / Sign-up / User ops / Vendors / Equipment / Materials / On-site execution / Photo & video / Lead conversion / Event recap

Output:
| Work module | Specific task | Owner | Support | Start | Deadline | Deliverable | Predecessor |

Keep it within truly important tasks. Don't split infinitely for show.

---

# Part 4: Run of Show

Generate a minute-level run of show for the event day.
Output:
| Time | Duration | Segment | On stage | Off stage | Owner | Materials/Equipment | Notes |

Must cover:
Staff arrival / Setup / Equipment test / Guest confirm / Check-in / Warm-up / Open / Core content / Interaction / Break / Conversion / Group photo / Dismissal / Teardown

If the plan has none of a segment, do not force it in.

---

# Part 5: Budget Framework

Generate a budget table by category:
Venue / Stage & equipment / Guests / Design & production / Promotion / Photo & video / Gifts / Catering / Staff / Transport / Other / Reserve

Output:
| Category | Item | Qty | Unit price | Estimated amount | Required/Optional | Note |

Important:
If I haven't given real quotes, do not fabricate local market prices.
Unit price and amount: 【quote pending】
If a total budget exists, also give recommended % allocation per category.

---

# Part 6: Materials Checklist

Output:
| Category | Material | Qty | Used in | Arrive by | Owner | Backup? |

Classify by: check-in / stage / guest / interactive props / promotion / staff / equipment / emergency supplies.

---

# Part 7: Risk Plan

Check:
People / Guests / Sign-ups / Attendance / Venue / Equipment / Network / Weather / Transport / Safety / Vendors / Flow overrun / Order / PR

Output:
| Risk | Probability | Impact | Warning signal | Prevention | Contingency | Owner |

List the ~10 most worth-attention items. Don't pad with low-probability ones.

---

# Part 8: Pre-event Final Checklist

A checklist the event lead can tick off the day before. Classify by:
Venue / People / Guests / Equipment / Materials / Content / Promotion / Sign-ups / Safety / Contingency

Use □ for each item. ≤30 items; each must be a clearly yes/no action.

---

# Final

From a "project manager" point of view, tell me:
If this event were tomorrow, what are the top 5 things to confirm first?
Rank by priority and explain why.

# Constraints

1. Don't invent real data I haven't provided.
2. Mark uncertain info 【to be confirmed】.
3. For safety, fire, venue regulations — only remind, don't fabricate specific requirements.
4. Tasks must land on specific owners.
5. Timeline must consider dependencies between tasks.
6. Plan must be directly usable by ordinary executors.

4 key tables (most used in execution plans)

Table 1 | Event timeline — minute-level:

Time	Task/Segment	Specific content	Owner	Notes
09:00–09:30	Check-in	Guest check-in, materials pickup, seat	Zhang San	Background music
09:30–09:40	Opening	Host intro, theme and flow	Li Si	Cap at 10 min
09:40–10:40	Keynote	Guest talk and case study	Wang Wu	Talk + Q&A
10:40–11:00	Tea break	Tea break, free exchange, group photo	Zhao Liu	Snacks and drinks

Table 2 | Task assignments — who owns what, deadline:

Task	Content	Owner	Support	Deadline
Promotion	Plan, post posters and articles	Zhang San	Li Si, Wang Wu	7 days before
Guest invite	Lock list, send invites, confirm	Li Si	Zhao Liu	10 days before
Materials	Design and produce, check quantity	Wang Wu	Zhang San, Zhao Liu	3 days before
On-site	Layout, flow control, contingency	Zhao Liu	Zhang San, Li Si	Event day

Table 3 | Resource requirements — what, from where:

Type	Resource	Qty	Owner	Source / Note
Venue	Multi-function hall	1	Zhang San	Booked, includes audio & projector
Equipment	LED screen	1 set	Li Si	Provided by venue
Materials	Check-in kit	100 sets	Wang Wu	In-house
People	Volunteers	10	Zhao Liu	Campus recruit

Table 4 | Budget breakdown — where the money goes:

Item	Budget (RMB)	Actual (RMB)	Note
Venue	6,000	5,800	Includes audio & projector
Guests	8,000	8,000	Transport + speaker fee
Materials	2,500	2,200	Poster + manual + kit
Catering	3,500	3,200	Tea break + drinks
Total	20,000	19,200	800 saved

Remember: tables = the tool for landing details; the clearer, the more efficient.

Run of Show deep-dive

Run of Show = the event's "director's script", minute-level actions and owners, to ensure smooth delivery.

Why bother?

Clarify start and end time for each segment
Everyone knows when and what to do
Predict risks in advance; respond fast on site
Make the experience smoother; maximize impact

Production tips:

Fine time granularity (10 min recommended)
Clear actions and outputs (what to do / say)
Named owners (who's responsible)
Materials and equipment ready (in position early)
Note risks and responses

Golden rule: the more thorough the prep, the calmer the on-site; the clearer the flow, the better the experience.

The flow isn't a dead script — micro-adjust by on-site rhythm, but key milestones never slip.

How to modify

What to change	How to change
Less than 30 days to event day	Change "T-30" to the actual countdown (e.g. "T-14") and scale the rest
Want only a subset (e.g. just budget / materials)	Delete other section headers; keep "Constraints"
Already have real quotes	Append them to the plan; this Prompt will read them automatically
Team roles already defined	At the top add: "Team roles: PM / Content / Design / On-site …" so AI assigns per that

How to verify

Output covers all 8 parts (一–八)
Each timeline task is directly executable, not "do promotion" placeholder
WBS work modules ≤ 15 (more is padding)
Run of Show covers the 14 standard segments
All budget unit prices / amounts are 【quote pending】, no AI-invented "market price"
Risk plan ≤ 12 items, no padded low-probability risks
Pre-event checklist ≤ 30 items
Final "if tomorrow" top-5 priorities

Pass standard: tomorrow, this plan can be used to kick off the first prep meeting, advancing from T-30 → T+7.

Real-output walkthrough (Attachment 3 | AI活动执行计划.md)

The execution plan that came out (excerpts):

Feasibility check: 8 risk categories identified, 3 high-severity (venue audio / guest schedule / budget)
Timeline: complete 10 milestones T-30 / T-21 / T-14 / T-7 / T-3 / T-1 / T / T+1 / T+3 / T+7
WBS: 14 work modules (project lead / guests / content / design / promotion / sign-up / materials / on-site / photo & video / lead conversion / recap …)
Run of Show: covers 14 standard segments, each 5–30 minutes
Budget: 12 categories (venue / stage & equipment / guests / design & production / promotion / photo & video / gifts / catering / staff / transport / other / reserve), all unit prices 【quote pending】
Materials: 8 categories (check-in / stage / guest / interactive props / promotion / staff / equipment / emergency supplies)
Risk plan: 10 top risks (guest no-show / low attendance / equipment failure / network outage / order …)
Pre-event checklist: 30 tickable items

Key design choices:

The point is not to keep thinking creatively but to break the plan into something ordinary executors can use
Each task is directly executable — "do promotion" became "finish the first round of posters, sign-up page, Moments copy"
All budget unit prices 【quote pending】 — AI didn't fabricate local market prices
Top 5 priorities — the final sprint checklist before T-1

Remember: the plan answers "what"; the execution plan answers "how" — a qualified project plan can run the first prep meeting tomorrow.

Three-Step Connection Cheatsheet

Handoff	Common mistake	Right move
A → B	Just copy AI's answer from Prompt A and move on	Check the AI-organized Brief is what you really want; if not, go back to A for one more round
B → C	Find a fatal flaw in the plan after Prompt C output, then re-run C	Go back to Prompt B to adjust the plan, then re-run C; don't patch C's output
Whole flow	Run each of the 3 prompts once and assume you're done	After Prompt C, when things change during prep, go back to B to adjust the plan, then re-run C for the new segment

Advanced: turn the 3 prompts into a Skill

The 3 prompts are separate — the real productivity boost is turning them into a Skill. 活动策划师 has scripted the three-step flow:

You just say the need ("next month a client appreciation event")
The Agent automatically runs A → B → C
Each step confirms back with you
At the end, you get a complete plan + project plan

8 scenario-specific follow-up templates (investment / anniversary / new product launch / industry conference / salon / awards / training / cross-border) are also included in the Skill's script library — once installed, just say "I want to run an investment event," and the Agent automatically uses the right script.

New to this? Scroll back up to the "Install the Skill" section above and follow the prompts.

What's Next

Lesson 3 "8 templates + 3 red lines + wrap-up" gives you 8 scenario-specific templates + 3 red lines you can't skip + 24 signature lines + 5 key formulas.
Jump directly to the assignment page to start practicing.

What This Lesson Is

Lesson 1 gave the "why" and the map. This lesson gives "how to do it."

We use a real event case ("Feifan Zhichuang · Future Partner AI Roadshow Day") to run the three prompts A / B / C end to end:

Hands-on 1 | Prompt A — Requirement clarification: turn a one-line ask into a structured Brief
Hands-on 2 | Prompt B — Plan design: 3 directions + evaluation + complete plan
Hands-on 3 | Prompt C — Execution plan: timeline / WBS / Run of Show / budget / materials / risks / pre-event checklist

Each prompt has 4 sections: when to use → full prompt text → how to modify → how to verify. Copy first, use second, modify third.

Install the Skill

Copy the prompt below to any SkillHub-compatible Agent to install automatically:

First check whether SkillHub is installed. If not, follow https://skillhub.cn/install/skillhub.md to install SkillHub (CLI only), then install the [活动策划师](https://skillhub.cn/skills/user_4fc8972a/ai-event-planner) skill. If already installed, directly install the [活动策划师](https://skillhub.cn/skills/user_4fc8972a/ai-event-planner) skill.

Once installed, use the prompt below to let the Agent first understand the Skill, then execute it step by step:

Read this file — it is a skill. Analyze what steps it contains, what the standard is for each step, and how I should work with you.

Case Background (Runs Through All 3 Steps)

To make the outputs comparable, here's the input:

Raw need (Prompt A's input):

Next month the company wants to host a 100-person offline AI-themed sharing event, hoping to lift brand visibility and pick up some leads.

Confirmed Brief highlights (Prompt A's output → Prompt B's input):

Event type: offline industry-sharing conference + VIP dinner
Scale: 100 main venue + 20–30 VIP dinner
Budget: ≤ 50K (hard cap)
Core goal: 30–50 qualified leads
Audience: founders, owners, managers across industries (mixed)
Key constraints: ~1 month to event, tight budget, mixed background (can't be too technical or too shallow)

The three attachments (inspected below) are the real outputs of this event — sanitized for reference:

AI活动策划Brief.md — Prompt A output
AI活动策划方案.md — Prompt B output
AI活动执行计划.md — Prompt C output

Hands-on 1 | Prompt A: turn a vague need into a professional Event Brief

What you'll learn on this page

Use AI to ask all the key questions in one pass (goals, audience, content, time, budget, format, resources, metrics)
Quickly sort requirements and constraints (avoid omissions, avoid back-and-forth, avoid late-stage reversals)
Output a clear Event Brief as the basis for the next step (with evidence, you can produce quality plans efficiently)

When to use

The boss / client / yourself drops a one-liner like "help me organize an event" or "next month we need an investment event"
Information is severely lacking; if you just hand it to AI for a plan, AI will fill in the blanks itself
You need an Event Brief that can flow through the team and be understood by everyone

Core moves (4 steps)

1. Assign a role     →  You are a senior event planning consultant
2. Don't plan yet    →  Don't write the event plan directly yet
3. Check info first  →  Verify goals, audience, time, location, budget, resources
4. Ask then output   →  3–5 key questions per round; once info is confirmed, generate the Event Brief

Full prompt

# Role

You are a senior event planning consultant with 10+ years of experience, specializing in corporate events, brand events, client events, industry conferences, training events, and offline salons.

Your task is NOT to immediately write me an event plan. Your task is to help me clarify the event requirements first.

# My Raw Need

【Paste the original event request from your boss, client, or yourself here】

Example:
Next month the company wants to host a 100-person offline AI-themed sharing event, hoping to lift brand visibility and pick up some leads.

# Your Task

First analyze my requirements.
Do not output a complete event plan yet.
Assess whether the current information is enough to plan the event, and find every important piece of missing information that could affect the plan's quality.

Focus on these dimensions:
1. Event goals
2. Target audience
3. Event scale
4. Time
5. City and venue
6. Budget
7. Existing company resources
8. Guest resources
9. Promotion channels
10. Desired business outcomes
11. Event format
12. Other constraints

# Step 1: Information Diagnosis

Output first:
| Information dimension | Currently known | Clear? | What still needs confirming |

Only list information that truly affects the event plan.

# Step 2: Ask Me Questions

Based on your assessment, ask me only the 3–5 most important questions per round.

Questions must:
1. Be understandable by a layperson
2. Offer choices where possible
3. Not ask 10+ questions at once
4. Prioritize information that will directly change the plan
5. Not repeat information already clear

After I answer, keep assessing whether to ask more.
Stop asking once you have enough information.

# Step 3: Generate the Event Brief

Once information is confirmed, organize it into an "Event Planning Brief":
## 1. Event basics
Event name:
Event type:
Event time:
Event location:
Event scale:

## 2. Event background
In ≤100 words, summarize why this event is being held.

## 3. Core goals
Distinguish:
Core goals:
Secondary goals:
Be specific — avoid empty phrases like "boost visibility".

## 4. Target audience
Core audience:
Audience profile:
Why they would attend:

## 5. Core event needs
List 3–5 items.

## 6. Budget and resources
Budget range:
Existing resources:
Resources to be acquired:

## 7. Constraints
Time, budget, venue, people, brand, etc.

## 8. Success metrics
Propose 5–8 measurable indicators. e.g. signups, attendees, attendance rate, qualified leads, engagement, social reach, satisfaction.

## 9. Items still to confirm
If any information is uncertain, list separately.

# Constraints

Do not make up facts I haven't provided.
Mark uncertain info explicitly as 【to be confirmed】.
Point out any obviously unreasonable or conflicting requirements.
Use professional but easy-to-understand language.

How to modify

What to change	How to change
Only one specific scenario (e.g. investment event / client appreciation / training)	In "Role", add: "This round focuses only on XX-type events"
Some info is already known (e.g. time and location are set)	In "My Raw Need", write confirmed info clearly to skip corresponding questions
Don't want to be asked too many questions	Change "ask only the 3–5 most important questions" to "ask only the 3 most critical"
Want a Brief without back-and-forth	In "Constraints", add: "If I mark 【use reasonable inference】, please infer and label 【to be confirmed】"

How to verify

After running once, check against this list:

Output an information diagnosis table (not a direct plan)
Questions capped at 3–5 per round, not 10+ at once
Multi-dimensional diagnosis, not just budget / time
Final Brief covers the full 一–九 structure
Uncertain items are marked 【to be confirmed】, no "I'll fill that in for you" inventions
Conflicts are actively flagged (e.g. 50K budget × full-day + VIP dinner × 100 people)

Pass standard: the Brief can be sent directly to a colleague / boss without re-explaining.

Real-output walkthrough (Attachment 1 | AI活动策划Brief.md)

The Brief that came out (key items):

Event type: 100-person offline AI-themed sharing
Core goals: lift brand awareness; acquire leads
Target audience: local SMB owners, managers, marketing/ops leaders
Event time: Saturday afternoon
Event budget: ≤ 30K
Existing resources: AI guest speakers, public WeChat, enterprise WeChat, private community
Key metrics: 100 signups ｜ 70 attendees ｜ 30 qualified leads

Key design choices:

Clarify first, then plan — AI didn't make up any key parameters
Budget 30K, tighter than the original "≤ 50K" — because AI asked "3K and 5K plans are very different, which one?"
70% attendance rate as a key metric — set after AI asked "what's your typical signup-to-attendance ratio?"
【to be confirmed】 kept on 5 items to avoid losing the basis during execution

Remember: a good start is half the battle! Clarify first, then think it through, then break it down.

Hands-on 2 | Prompt B: brainstorm → compare → deepen into a complete plan

What you'll learn on this page

6 directions to let AI "think it through" (participant experience / content & flow / promotion / venue / risk / budget)
Generate 3 different plans in one go, compare, pick the best
"AI recommends + human decides" 4-step decision method
Form a complete event plan ready to hand to the execution team

When to use

Already have a confirmed Event Brief
Want to see 3 different directions, not just AI's default
Need a complete plan that can move into execution

Full prompt

# Role

You are a senior brand event planning director, with experience in marketing, user ops, content, and offline event execution.

Your task is to design a truly attractive, viral, and executable event for me, based on the Brief below.

# Event Brief

【Paste the final Event Brief from Hands-on 1】

# Stage 1: Don't write a full plan yet

First propose 3 distinctly different event planning directions.

Don't just rename things.
The 3 plans should differ clearly in core idea, event format, interaction model, or viral logic.

Output as:
| Plan | Theme | One-line idea | Core play | Highlight | Why it fits | Potential issues |

# Stage 2: Plan evaluation

Score the 3 plans on these dimensions, 0–10 each:
1. Fit to event goals
2. Appeal to target audience
3. Creativity
4. Virality
5. Interactivity
6. Business conversion potential
7. Execution difficulty
8. Cost control
9. Risk level

Output:
| Dimension | Plan A | Plan B | Plan C |
|---|---:|---:|---:|

Note:
For execution difficulty and risk, clarify whether "higher score = easier" or "higher score = riskier" to avoid ambiguity.

Finally give:
Recommended plan:
Why:
Highlights to absorb from the other two:

# Stage 3: Generate the complete plan

Based on the recommended plan and absorbing worth-keeping parts from the others, output a complete event plan:

# 《XXXX Event Plan》
## 1. Event background
Why this event. ≤200 words.

## 2. Event goals
Brand goals
User goals
Business goals
Quantify each.

## 3. Event theme
Main title:
Subtitle:
Slogan:
Core idea:

## 4. Target audience
Core users:
User profile:
Core needs:
Reasons to attend:

## 5. Event basics
Time:
Location:
Scale:
Format:
Duration:

## 6. Overall event design
A paragraph explaining the core logic of the whole event.

## 7. Event highlights
3–5 truly perceivable highlights. Avoid empty phrases like "rich content", "varied formats", "full of insights".

## 8. Run of show
First, the high-level flow.
| Time | Segment | Content | Purpose |

## 9. Key segment design
Expand the 3–5 most important segments:
Segment name:
Play:
Participation:
Required resources:
Expected effect:

## 10. Guest and content design
What kinds of guests are needed.
Do not fabricate real people.
Explain what content role each type of guest plays.

## 11. User interaction design
Consider separately:
Before check-in
During the event
After the event
How to lift participant engagement.

## 12. Promotion plan
Across:
Pre-launch
Sign-up period
Final sprint
Event day
Post-event

## 13. Sign-up and conversion design
If the event has lead or conversion goals, design a natural path. Focus on:
Why users leave contact info.
Why they would inquire further.
How to follow up after the event.
Avoid hard selling.

## 14. Effectiveness evaluation
Key post-event metrics.

## 15. Plan risk check
Stand in three roles to check the plan once:
Client lead
Execution lead
Ordinary attendee
Each lists their top 3 likely questions.

# Constraints

1. All content must match the Brief.
2. Do not exceed the budget.
3. Mark uncertain info 【to be confirmed】.
4. Do not fabricate venue quotes, guest prices, policy requirements.
5. All ideas must consider real execution difficulty.
6. Few empty slogans, many concrete actions.
7. Output must be understandable by ordinary executors.

6 directions to let AI "think it through"

#	Direction	Focus
01	Participant experience	The full journey from entry to exit; which segments wow, which lose them; how to lift satisfaction and interaction
02	Content & flow details	Whether each segment's content is reasonable; whether time allocation is right; whether transitions are smooth
03	Virality & influence	How to design viral highlights and topics; social path and diffusion design; how to extend the event's influence cycle
04	Venue & atmosphere	Whether the venue is comfortable and accommodating; lighting / audio / stage design; on-site decor and detail optimization
05	Risk & contingency	What risks could appear; the contingency system and owners; how to lower the chance of mistakes
06	Budget & resource optimization	Whether the budget allocation is reasonable; what can be swapped or optimized; how to achieve goals at lower cost

AI tip: thinking it through is about empathy + breaking down details + predicting risks — AI helps you find the blind spots you didn't think of.

Generate 3 different plans in one go

Why generate multiple plans? — broaden ideas + compare trade-offs + reduce bias + faster decisions.

Real case: after running 3 directions, AI returned:

Dimension	Plan A — Solid & Steady	Plan B — Interactive	Plan C — Light & Viral
Positioning	Professional content & deep experience	Strengthen participation and immersion	Lightweight, viral, low-barrier participation
Core highlight	Insight + deep interaction	Strong interaction + scene-based experience	Lightweight content + viral spread
Format	Keynote + roundtable + workshop	Interactive game + experience zone + check-in tasks	Online live + community interaction + giveaway
Best for	Industry forum, professional summit	Brand event, user carnival	Online event, brand promotion
Strengths	Deep content; long-term professional influence	Lively atmosphere; viral; fits younger audience	Wide reach; cost-controlled; flexible
Possible challenges	Long prep; traditional format	High execution detail; large venue & staff	Limited interaction depth; weaker stickiness

Remember: there is no best plan, only the most fitting. AI gives you choices, you make the call.

AI provides information, plans, and suggestions, but can't take responsibility for you. Combine goals, resources, and risks to make the most fitting choice.

Four-step decision method:

Align goals — which plan best achieves the event goals?
Assess resources — can the team, budget, time, and venue support it?
Compare risks — what are the risk points? What's the backup?
Decide — make the choice, clarify execution and ownership!

Caution: don't over-rely on AI

AI has no situational awareness: it can't predict sudden on-site changes
AI has no values: it can't judge long-term brand–user relationships for you
AI doesn't bear responsibility: the final result, good or bad, is on the decision-maker

AI is your advisor, not your boss. You decide, you own the outcome, you take the credit!

How to modify

What to change	How to change
Want more directions (4 or 5)	In "Stage 1", change "3" to "4" or "5"
Don't want 9-dimension evaluation	In "Stage 2", drop unnecessary dimensions, keep 3–5 most important
Already have a direction in mind	At the top, add: "After listing 3 directions, focus on deepening Plan X"
Very tight budget	In "Constraints", add: "Any budget item over 20% of total budget must be marked 【to be confirmed】"
Want a shorter plan	In "Constraints", add: "Keep the plan under 5000 words; key segments ≤4"

How to verify

Stage 1 outputs 3 clearly different directions, not "three similar names"
Stage 2 scores 9 dimensions and clarifies the "score direction"
Recommended plan + reason + highlights to absorb from others is given
Stage 3 plan covers the full 一–十五 structure
Highlights avoid empty phrases ("rich content", etc.)
Risk check covers client / execution / attendee perspectives

Pass standard: the plan can be handed directly to the execution team to start prep, no need to ask "so what do we do".

Real-output walkthrough (Attachment 2 | AI活动策划方案.md)

The plan that came out (key items):

#1 Event goals: strengthen community engagement and member interaction; lift participation and belonging; add 200+ valid users; boost content interaction 30% during the event; accumulate quality content for later conversion
#2 Core idea: "Community Energy Station" — check in together, grow together, shine together; theme = check-in tasks + topic interaction + energy ranking + lucky draw & sharing
#5 Key flow: warm-up (3 days) → ignition (7 days) → climax (3 days) → wrap-up (2 days)
#10 Plan outline: background & goals / theme / target users / core idea / run of show / interaction design / promotion / commercial conversion / budget / metrics (10 modules)

Key design choices:

Clear goals: direction doesn't drift
Creativity solidified: highlights stand out
Executable plan: ready to land
AI drafts first, human judges and optimizes

Remember: the more thoroughly you think it through, the smoother the execution, the better the result. 10 minutes of thinking saves 10x the time and cost later.

Hands-on 3 | Prompt C: turn the plan into an executable project plan

What you'll learn on this page

Six execution questions to break the plan into a landing-ready execution plan
4 key tables: event timeline / task assignments / resource requirements / budget breakdown
Run of Show deep-dive: keep the on-site calm, in order, and engaged
A work plan that ordinary executors can use directly

When to use

Already have a finalized event plan
Entering prep period, going from "plan" to "project plan"
You want AI as a "project manager" not a "planning director"

Six execution questions

The plan answers "what"; the execution plan answers "how".

1. Who does it?       →  Clear people and roles
2. When?              →  Reverse-engineer timeline and milestones
3. How much money?    →  Budget framework and cost control
4. What to prepare?   →  Materials, venue, equipment, guests
5. How to run it?     →  Run of Show and on-site rhythm
6. What if it goes wrong? →  Risk and contingency plans

Full prompt

# Role

You are an event project manager with rich offline event execution experience.
You are taking over a finalized event plan.
Your goal is NOT to keep generating ideas, but to break the plan into a truly executable, checkable, pushable project plan.

# Event Plan

【Paste the final plan from Hands-on 2】

# Current requirement

Do an execution feasibility check on the plan, then complete the following.

---

# Part 1: Execution Feasibility Check

Check the plan for these issues:
1. Missing information
2. Time conflicts
3. Resource shortfalls
4. Budget risks
5. Staffing risks
6. Venue risks
7. Equipment risks
8. Guest risks
9. User experience risks
10. Safety risks

Output:
| Issue | Severity | Why it's an issue | Suggested fix |

Severity: High / Medium / Low
Mark unknown info as 【to be confirmed】.

---

# Part 2: Event Prep Timeline

Take the event day as T.
Count backward from T-30.
Include at least: T-30 / T-21 / T-14 / T-7 / T-3 / T-1 / T / T+1 / T+3 / T+7

Output:
| Milestone | Core goal | Specific task | Output | Owner role |

Tasks must be concrete enough to execute.
Not "do promotion" — instead "finish the first round of posters, sign-up page, and WeChat Moments copy, then start the first round of channel posting."

---

# Part 3: WBS Breakdown

Break the event down into concrete tasks. At minimum cover:
Project lead / Venue / Guests / Content / Design / Promotion / Sign-up / User ops / Vendors / Equipment / Materials / On-site execution / Photo & video / Lead conversion / Event recap

Output:
| Work module | Specific task | Owner | Support | Start | Deadline | Deliverable | Predecessor |

Keep it within truly important tasks. Don't split infinitely for show.

---

# Part 4: Run of Show

Generate a minute-level run of show for the event day.
Output:
| Time | Duration | Segment | On stage | Off stage | Owner | Materials/Equipment | Notes |

Must cover:
Staff arrival / Setup / Equipment test / Guest confirm / Check-in / Warm-up / Open / Core content / Interaction / Break / Conversion / Group photo / Dismissal / Teardown

If the plan has none of a segment, do not force it in.

---

# Part 5: Budget Framework

Generate a budget table by category:
Venue / Stage & equipment / Guests / Design & production / Promotion / Photo & video / Gifts / Catering / Staff / Transport / Other / Reserve

Output:
| Category | Item | Qty | Unit price | Estimated amount | Required/Optional | Note |

Important:
If I haven't given real quotes, do not fabricate local market prices.
Unit price and amount: 【quote pending】
If a total budget exists, also give recommended % allocation per category.

---

# Part 6: Materials Checklist

Output:
| Category | Material | Qty | Used in | Arrive by | Owner | Backup? |

Classify by: check-in / stage / guest / interactive props / promotion / staff / equipment / emergency supplies.

---

# Part 7: Risk Plan

Check:
People / Guests / Sign-ups / Attendance / Venue / Equipment / Network / Weather / Transport / Safety / Vendors / Flow overrun / Order / PR

Output:
| Risk | Probability | Impact | Warning signal | Prevention | Contingency | Owner |

List the ~10 most worth-attention items. Don't pad with low-probability ones.

---

# Part 8: Pre-event Final Checklist

A checklist the event lead can tick off the day before. Classify by:
Venue / People / Guests / Equipment / Materials / Content / Promotion / Sign-ups / Safety / Contingency

Use □ for each item. ≤30 items; each must be a clearly yes/no action.

---

# Final

From a "project manager" point of view, tell me:
If this event were tomorrow, what are the top 5 things to confirm first?
Rank by priority and explain why.

# Constraints

1. Don't invent real data I haven't provided.
2. Mark uncertain info 【to be confirmed】.
3. For safety, fire, venue regulations — only remind, don't fabricate specific requirements.
4. Tasks must land on specific owners.
5. Timeline must consider dependencies between tasks.
6. Plan must be directly usable by ordinary executors.

4 key tables (most used in execution plans)

Table 1 | Event timeline — minute-level:

Time	Task/Segment	Specific content	Owner	Notes
09:00–09:30	Check-in	Guest check-in, materials pickup, seat	Zhang San	Background music
09:30–09:40	Opening	Host intro, theme and flow	Li Si	Cap at 10 min
09:40–10:40	Keynote	Guest talk and case study	Wang Wu	Talk + Q&A
10:40–11:00	Tea break	Tea break, free exchange, group photo	Zhao Liu	Snacks and drinks

Table 2 | Task assignments — who owns what, deadline:

Task	Content	Owner	Support	Deadline
Promotion	Plan, post posters and articles	Zhang San	Li Si, Wang Wu	7 days before
Guest invite	Lock list, send invites, confirm	Li Si	Zhao Liu	10 days before
Materials	Design and produce, check quantity	Wang Wu	Zhang San, Zhao Liu	3 days before
On-site	Layout, flow control, contingency	Zhao Liu	Zhang San, Li Si	Event day

Table 3 | Resource requirements — what, from where:

Type	Resource	Qty	Owner	Source / Note
Venue	Multi-function hall	1	Zhang San	Booked, includes audio & projector
Equipment	LED screen	1 set	Li Si	Provided by venue
Materials	Check-in kit	100 sets	Wang Wu	In-house
People	Volunteers	10	Zhao Liu	Campus recruit

Table 4 | Budget breakdown — where the money goes:

Item	Budget (RMB)	Actual (RMB)	Note
Venue	6,000	5,800	Includes audio & projector
Guests	8,000	8,000	Transport + speaker fee
Materials	2,500	2,200	Poster + manual + kit
Catering	3,500	3,200	Tea break + drinks
Total	20,000	19,200	800 saved

Remember: tables = the tool for landing details; the clearer, the more efficient.

Run of Show deep-dive

Run of Show = the event's "director's script", minute-level actions and owners, to ensure smooth delivery.

Why bother?

Clarify start and end time for each segment
Everyone knows when and what to do
Predict risks in advance; respond fast on site
Make the experience smoother; maximize impact

Production tips:

Fine time granularity (10 min recommended)
Clear actions and outputs (what to do / say)
Named owners (who's responsible)
Materials and equipment ready (in position early)
Note risks and responses

Golden rule: the more thorough the prep, the calmer the on-site; the clearer the flow, the better the experience.

The flow isn't a dead script — micro-adjust by on-site rhythm, but key milestones never slip.

How to modify

What to change	How to change
Less than 30 days to event day	Change "T-30" to the actual countdown (e.g. "T-14") and scale the rest
Want only a subset (e.g. just budget / materials)	Delete other section headers; keep "Constraints"
Already have real quotes	Append them to the plan; this Prompt will read them automatically
Team roles already defined	At the top add: "Team roles: PM / Content / Design / On-site …" so AI assigns per that

How to verify

Output covers all 8 parts (一–八)
Each timeline task is directly executable, not "do promotion" placeholder
WBS work modules ≤ 15 (more is padding)
Run of Show covers the 14 standard segments
All budget unit prices / amounts are 【quote pending】, no AI-invented "market price"
Risk plan ≤ 12 items, no padded low-probability risks
Pre-event checklist ≤ 30 items
Final "if tomorrow" top-5 priorities

Pass standard: tomorrow, this plan can be used to kick off the first prep meeting, advancing from T-30 → T+7.

Real-output walkthrough (Attachment 3 | AI活动执行计划.md)

The execution plan that came out (excerpts):

Feasibility check: 8 risk categories identified, 3 high-severity (venue audio / guest schedule / budget)
Timeline: complete 10 milestones T-30 / T-21 / T-14 / T-7 / T-3 / T-1 / T / T+1 / T+3 / T+7
WBS: 14 work modules (project lead / guests / content / design / promotion / sign-up / materials / on-site / photo & video / lead conversion / recap …)
Run of Show: covers 14 standard segments, each 5–30 minutes
Budget: 12 categories (venue / stage & equipment / guests / design & production / promotion / photo & video / gifts / catering / staff / transport / other / reserve), all unit prices 【quote pending】
Materials: 8 categories (check-in / stage / guest / interactive props / promotion / staff / equipment / emergency supplies)
Risk plan: 10 top risks (guest no-show / low attendance / equipment failure / network outage / order …)
Pre-event checklist: 30 tickable items

Key design choices:

The point is not to keep thinking creatively but to break the plan into something ordinary executors can use
Each task is directly executable — "do promotion" became "finish the first round of posters, sign-up page, Moments copy"
All budget unit prices 【quote pending】 — AI didn't fabricate local market prices
Top 5 priorities — the final sprint checklist before T-1

Remember: the plan answers "what"; the execution plan answers "how" — a qualified project plan can run the first prep meeting tomorrow.

Three-Step Connection Cheatsheet

Handoff	Common mistake	Right move
A → B	Just copy AI's answer from Prompt A and move on	Check the AI-organized Brief is what you really want; if not, go back to A for one more round
B → C	Find a fatal flaw in the plan after Prompt C output, then re-run C	Go back to Prompt B to adjust the plan, then re-run C; don't patch C's output
Whole flow	Run each of the 3 prompts once and assume you're done	After Prompt C, when things change during prep, go back to B to adjust the plan, then re-run C for the new segment

Advanced: turn the 3 prompts into a Skill

The 3 prompts are separate — the real productivity boost is turning them into a Skill. 活动策划师 has scripted the three-step flow:

You just say the need ("next month a client appreciation event")
The Agent automatically runs A → B → C
Each step confirms back with you
At the end, you get a complete plan + project plan

New to this? Scroll back up to the "Install the Skill" section above and follow the prompts.

What's Next

Lesson 3 "8 templates + 3 red lines + wrap-up" gives you 8 scenario-specific templates + 3 red lines you can't skip + 24 signature lines + 5 key formulas.
Jump directly to the assignment page to start practicing.

Table of Contents

Three hands-on: 3 prompts end to end

Table of Contents