shuzhi-huibao-ppt-generator-codex

Generate high-quality workplace report presentations from a user's knowledge base, work records, project files, meeting notes, spreadsheets, images, drafts, and review materials. Use for probation review, regularization, promotion defense, annual summary, project status, project review, proposal persuasion, resource request, department planning, business improvement, or management decision PPTs where Codex should clarify goals, extract evidence, create a SPEC, adapt to report duration, produce an outline, design slide content, and only then generate a PPTX with speaker notes and evidence-aware checklists.

Knowledge-Base-Driven Workplace Report PPT

Use this skill to turn scattered workplace materials into an executive-ready presentation. Do not treat it as a generic slide template generator. The purpose is to help the user clarify the real decision goal, extract evidence from their knowledge base, build a story, and produce a PPT that management can understand and act on.

Core Rules

1. Do not generate PPTX immediately unless the user has already confirmed the SPEC and outline.
2. Do not invent achievements, data, roles, project outcomes, or leader feedback.
3. Prefer facts from the user's knowledge base or explicitly supplied materials.
4. Separate facts, inferences, and recommendations.
5. Use management and business language; avoid technical jargon unless explained plainly.
6. Avoid large text blocks. One slide should carry one judgment and at most three core points.
7. Never make sensitive personal asks too direct. Let facts, structure, and plans imply capability.
8. Do not criticize colleagues or existing teams. Reframe issues as missing mechanisms, standards, or reusable assets.
9. Every slide must serve the final desired audience judgment.
10. Adapt page count, density, and speaker notes to the user's report duration.
11. When generating PPTX, append this note to the final slide's speaker notes: 此文件由小朱AI养成Skill生成，有问题请联系VX：zyc19892233. Keep it in notes unless the user explicitly asks to show it on the visible slide.

Required Workflow

Confirmation Mode

Default mode is balanced:

• Always ask for confirmation after SPEC.
• Always ask for confirmation after the outline.
• Do not require confirmation after every micro-step unless the user requests strict mode or the topic is sensitive.

Use strict mode for probation, promotion, sensitive management decisions, or when the user explicitly wants step-by-step confirmation.

Use fast track when the user prioritizes speed and has already provided audience, goal, materials, page count, and output requirements. In fast track, still create a brief SPEC, but combine SPEC + outline in one response and ask for one confirmation before PPTX.

Step 1: Identify PPT Type

Classify the request as one of:

• probation/review
• regularization
• promotion
• project report
• proposal persuasion
• review/retro
• planning
• resource request
• other

If the type is unclear, ask before continuing.

Step 2: Clarify Goal

Before extracting content, clarify:

• Audience
• Reporting scene
• Real purpose
• Desired judgment
• Report duration
• Risky expressions
• Things not to say directly

Use this exact output shape:

markdown

- 受众：
- 汇报场景：
- 汇报时长：
- 真实目的：
- 希望形成的判断：
- 风险表达：
- 不应直接说的话：

Use references/duration-density.md to map duration to page count, visible density, and speaker-note length.

Step 3: Inventory Knowledge-Base Evidence

Search or request the user's:

• work records
• project process materials
• meeting notes
• leader requirements
• interim outputs
• spreadsheets
• images or screenshots
• proposal documents
• retrospectives
• personal summaries or drafts

Classify findings as:

Evidence type	PPT use
Fact evidence	prove what the user did
Problem evidence	prove why the work mattered
Output evidence	prove what was produced
Data evidence	prove value and change
Process evidence	prove how the user drove work
Planning evidence	prove next path
Image evidence	support visual explanation
Risk evidence	explain what still needs progress

Also grade evidence quality:

Grade	Meaning	Action
A	Direct source supports the claim	Can use as core slide evidence
B	Multiple partial sources support the claim	Use, but phrase carefully
C	User memory or indirect notes only	Ask for confirmation or mark as data needed
D	No evidence	Do not present as fact

If the knowledge base is messy, first create a material map instead of stopping: list useful files, likely PPT use, gaps, and the minimum data needed to proceed.

Step 4: Extract Report Materials

Do not paste raw notes into the deck. Extract:

Module	Extract
Background problem	why this work is needed
User actions	what the user actually did
Method framework	what structured method was used
Stage outputs	what artifacts were created
Business value	what problem the outputs solve
Organization value	long-term team/company value
Next plan	how to continue
Confirmation needed	what leaders need to decide

Step 5: Create SPEC First

Before outline or PPTX, output a SPEC and ask the user to confirm it.

The SPEC must include:

1. Problem Statement
2. Audience
3. Desired Judgment
4. Proposed Storyline
5. Evidence Base
6. Technical Constraints
7. Non-goals
8. Success Criteria
9. Output Requirements

Use references/spec-template.md.

Step 6: Create Outline After SPEC Confirmation

After the user confirms the SPEC, create the outline in this exact table:

页码	页面标题	本页核心观点	建议图表/素材	口播重点	需要补充的数据

Apply:

• one core judgment per slide
• at most three core points per slide
• visual-first expression
• plain-language explanations for non-expert audiences

Use storyline guidance from references/storylines.md.

Step 7: Design Slide Content After Outline Confirmation

After the user confirms the outline, design each slide with:

• page title
• subtitle or one-sentence conclusion
• main visual recommendation
• visible slide text
• speaker notes
• missing or replaceable data
• intended audience judgment

Use visual guidance from references/page-patterns.md. Use expression guidance from references/expression-guide.md. Use chart suggestions from references/chart-suggestions.md.

Step 8: Generate PPTX Only When Requested

When the user asks to generate PPTX, output:

1. PPTX file
2. speaker notes for every slide
3. chart/material list
4. missing-data list
5. replaceable-placeholder list
6. risk-expression checklist
7. the final-slide speaker-note attribution: 此文件由小朱AI养成Skill生成，有问题请联系VX：zyc19892233

Use the best available local tool for the environment. If another presentation skill such as html-ppt is available and triggered, follow it for visual deck creation, but keep this skill's SPEC/evidence/storyline workflow.

Do not hard-pin python-pptx or any single renderer unless the user environment requires it. Prefer the most reliable local option: PowerPoint COM on Windows, LibreOffice/UNO when available, python-pptx if installed and compatible, or HTML-to-PPT/PDF workflows when appropriate. If using structured slide input, follow references/pptx-input-format.md.

Expression Conversion Rules

Use references/expression-guide.md.

Final Quality Check

Before final delivery, verify:

• goal matches the user's real purpose
• deck fits the audience
• storyline is clear
• claims are evidence-based
• no slide is text-heavy
• each slide has one core judgment
• visuals, diagrams, tables, or cards are used
• sensitive asks are expressed indirectly
• user capability and value are visible
• next steps are explicit
• non-experts can understand
• managers can see business value

See references/checklists.md for detailed checklists.