Operations & Content
Year-End Stage Review (CN-only)#stage review#year-end#reportingYear-End Stage Review · CN-context
CN-only · Compress a full year of projects, KPIs, missteps, and growth into a stage-ready 500-700 word year-end review — first draft in 30 min, polished in 2 hours.
Pain addressed · Year-end review season hits: 'we said we'd cut cost 50% and we got 35% — how do I tell that story without crashing or stacking KPI buzzwords.'
Year-End Stage Review · CN-context
CN-only prompt. See prompt_zh for the full version. This scenario (nianzhongshuzhi · year-end stage review with PPT + Q&A) is a China-specific workplace ritual: department-level oral review delivered in late November through January, usually in front of your director and skip-level, scored on judgment + delivery, not just on KPIs.
If you're outside China and want the closest equivalent, use the "operations-weekly-recap" prompt scaled to annual, plus an "annual self-review" framing. The structure (1 conclusion + 3 numbers + 1 reflection + 1 next focus) still applies; only the cultural varnish differs.Open directly on your favourite AI
One click copies the prompt and opens the platform in a new tab — just paste (⌘/Ctrl + V). Recommended platforms are ordered by content fit.
Workflow · 5 steps
- 1
This scenario is a Chinese-specific stage review (nianzhongshuzhi). If you're outside CN, use operations-weekly-recap scaled to annual instead.
- 2
If you're writing one anyway: dump everything from the year into one block — OKR completion, project milestones, missteps, growth moments. Mess is fine.
- 3
Run the prompt in Kimi or Doubao (best Chinese phrasing). Replace {paste_yearly_log}.
- 4
On the first draft, edit four things: the opening sentence (make it something you'd actually say to your director), the three metric numbers, the reflection (only real mistakes, not 'I'm a perfectionist'), and the one focus for next year.
- 5
Pair the script with a 5-7 slide deck, one paragraph per slide. Pre-write answers to the three sharpest questions your skip-level might fire.
Verify before you ship
AI's "almost right" is the #1 pain. Tick these off so reviewers can't find the obvious holes. (Checkbox state stays local — we don't track it.)
Why this prompt works
This prompt isn't a generic “write me a Year-End Stage Review (CN-only)”. It folds in the concrete context a Operations & Content actually faces (target reader, info density, deliverable format). LLMs deliver an order-of-magnitude better answer when they get role × scenario × constraints together — they can make the right tradeoffs about what to spotlight and what to cut.
When to use
Best moment: you know roughly that you need to do a Year-End Stage Review (CN-only), but you're stuck on “how do I even ask the AI?” Muscle memory has no template. Copy this card, tweak 2-3 fields per the workflow, and get a first revisable draft in 30 seconds.
Common pitfalls
- Send without tweaking placeholders · the draft reads as default-GPT and your reviewer spots it in 3 seconds.
- Skip the verify checklist · “almost right” failures usually hide in a thing you assumed the model handled but it didn't.
- Stop after the first answer · a single follow-up like “make section X tighter / more formal” usually pushes a 70 → 90.
Variants & extensions
Want to use this card more aggressively? Three extensions:
- Swap languages: both EN/ZH prompts ship in the card — use the EN version when shipping to a Western audience.
- Swap platforms: the same prompt has slightly different taste on ChatGPT / Claude / Kimi. The recommended-platform pill marks the best fit.
- Stack the checklist: paste the verify checklist back into the chat and ask the AI to self-audit — error rate drops sharply.
Want 25 more prompts like this one?
Get the full 50-card Pro deck — multi-step chains, vertical variants, lifetime updates.
- 50 prompts · 25 free + 25 advanced multi-step chains
- PDF printable + Notion template
- Lifetime updates · ~5 new prompts a month, auto-synced
- Dual-language · EN/CN + 5 China-exclusive scenarios
