Skip to content
cccskills
FreePublished on GitHub

cn-fupan

Run a 复盘 (fupan), the structured project review widely used in Chinese companies: review the goal, assess the result, analyse why, and draw rules for next time, with a blame-free tone and owned actions. Use when asked 帮我做复盘, 项目复盘, 活动复盘, 复盘会怎么开, or a fupan or retrospective in Chinese. Produces the 复盘 document in Chinese with goal versus result, root causes split into controllable and uncontrollable, lessons stated as reusable rules, and an action list with owners and dates, plus a meeting agenda.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md4.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

复盘 (Fupan)

复盘 comes from Go players replaying a game to learn from it. In Chinese companies it is the standard way to review a project, a campaign or a launch, whatever the outcome. Its four steps are well known: 回顾目标, 评估结果, 分析原因, 总结规律. The value is in the last step, turning one experience into a rule the team can reuse. This skill runs all four and keeps the tone blame-free.

Write the output in Simplified Chinese unless asked otherwise. For an incident postmortem, see incident-postmortem; for a sprint retrospective, see retro-analysis.

What This Skill Produces

  • The 复盘 document in the four standard steps
  • Root causes, split into controllable and uncontrollable
  • Lessons as rules: each stated so the team can apply it next time
  • Actions with owners and dates
  • A meeting agenda if the 复盘 is held as a group session

Required Inputs

Ask for these if not provided:

  • What is being reviewed: project, campaign, launch, quarter
  • The original goal, with the numbers set at the start
  • The actual result, with the same numbers
  • The timeline and key decisions
  • Who took part, and whether this is for a group meeting or an individual review

Framework

  1. 回顾目标 (review the goal): what was the goal, exactly, and how was success defined at the time? If the goal was vague, say so; that is itself a finding.
  2. 评估结果 (assess the result): actual against target, metric by metric. Highlights (亮点) and shortfalls (不足), both with evidence.
  3. 分析原因 (analyse why): for each big gap or success, ask "why" until reaching a cause the team could act on. Split into:
    • 主观 / 可控: decisions, process, preparation
    • 客观 / 不可控: market, policy, external events. Name them, then move on; dwelling here teaches nothing.
  4. 总结规律 (draw the rules): each lesson as a rule: "当 [situation] 时,应该 [action],因为 [reason]". A good rule would change a future decision.
  5. 行动计划: what changes now, with an owner and a date.

Tone: discuss decisions and systems, not people. "评审环节缺少数据验证" rather than "某某没有看数据".

Output Format

复盘:[项目 / 活动名称]|[日期]

一、回顾目标 | 目标 | 当初的衡量标准 | 目标值 |

二、评估结果 | 指标 | 目标值 | 实际值 | 完成率 | 说明 |

  • 亮点:...
  • 不足:...

三、分析原因 | 现象 | 根本原因 | 主观可控 / 客观不可控 |

四、总结规律

  1. 当 [情况] 时,应该 [做法],因为 [原因]。

五、行动计划 | 行动 | 负责人 | 完成时间 |

附:复盘会议议程(如需要,60 分钟)

Quality Checks

  • The original goal is stated with its original numbers
  • Every large gap has a root cause that is actionable
  • Controllable and uncontrollable causes are separated
  • Every lesson is phrased as a reusable rule
  • Every action has an owner and a date
  • No individual is blamed by name

Anti-Patterns

  • 只复盘失败. Successes hide lessons too; review them the same way.
  • Stopping at "客观原因". If every cause is external, the team learns nothing.
  • Lessons as slogans ("加强沟通"). A rule says when and what to do.
  • Blame. It ends honest discussion at the next 复盘.

Example Trigger Phrases

  • "帮我做一下双十一活动的复盘。"
  • "项目延期了,帮我写复盘报告。"
  • "复盘会怎么开?给我一个议程。"
  • "Run a fupan on our product launch, in Chinese."

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 23, 2026

See all skills by mohitagw15856

Report a problem with this skill