Skip to content

AI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio narration from speaker notes, and support for your own .pptx templates. · by Hugo He

docs(quick-generate): define autonomous capability-complete flow

hugohe3ce836b2405b7
diff --git a/AGENTS.md b/AGENTS.md
index f295ffd6..fbd2db92 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -13,7 +13,7 @@ PPT Master turns source material into natively editable DrawingML PPTX. Generate
- Topic-only or fact-insufficient inputs run [`topic-research`](skills/ppt-master/workflows/stages/topic-research.md) in Generate Step 1; facts only, no images.
- Raw PPTX template plus new material/topic routes to [`template-fill-pptx`](skills/ppt-master/workflows/template-fill-pptx.md), not the SVG pipeline.
- Raw PPTX cannot be consumed as a Generate Step 3 SVG template; run [`create-template`](skills/ppt-master/workflows/create-template.md) first and return with the generated template workspace root. Never add Master/Layout structure directly to an existing PPTX/SVG; generate new structured SVG pages from the workspace.
-- Explicit quick/fast or skip-strategy generation may use [`quick-generate`](skills/ppt-master/workflows/profiles/quick-generate.md): prepare sources and page resources as needed, let the current agent decide without interaction, omit Strategist/confirmation/spec/lock, hand-author `svg_output/`, and export directly.
+- Explicit quick/fast or skip-strategy generation may use [`quick-generate`](skills/ppt-master/workflows/profiles/quick-generate.md): prepare sources/resources as needed, decide without interaction, omit Strategist/confirmation/spec/lock, hand-author `svg_output/`, pass its lockless final checker, and export.
- PPTX beautify is a strict 1:1 main-generation [`profile`](skills/ppt-master/workflows/profiles/beautify-pptx.md), not a separate route; any split/merge/drop/reorder uses the default main-pipeline policy.
- Finished PPTX native enhancement uses [`native-enhance-pptx`](skills/ppt-master/workflows/native-enhance-pptx.md) and must not enter SVG regeneration.
- [`visual-review`](skills/ppt-master/workflows/stages/visual-review.md), [`customize-animations`](skills/ppt-master/workflows/stages/customize-animations.md), and [`generate-audio`](skills/ppt-master/workflows/stages/generate-audio.md) are supporting stages; their trigger rules remain explicit/conditional.
diff --git a/README.md b/README.md
index 467783cc..9175f874 100644
--- a/README.md
+++ b/README.md
@@ -316,7 +316,7 @@ AI: Sure. Let's confirm the design spec:
The AI handles everything — content analysis, visual design, SVG generation, and PPTX export.
-> **Output:** The SVG pipeline has one PPTX converter: it reads `svg_output/` and writes a directly editable native DrawingML deck to `exports/<name>_<timestamp>.pptx`. The default Generate flow runs `finalize_svg.py`, produces self-contained previews in `svg_final/`, and snapshots `svg_output/` to `backup/<timestamp>/svg_output/`; PowerPoint's manual **Convert to Shape** command is outside the supported contract. Explicit [quick generation](./skills/ppt-master/workflows/profiles/quick-generate.md) still converts sources, researches factual gaps, and prepares required images, icons, formulas, and resource manifests when needed. The current agent makes the content, page, visual, and resource decisions in context, skips Strategist, confirmation, `design_spec.md`, and `spec_lock.md`, then hand-authors the SVG pages and exports one PPTX without preview, notes, validation reports, or backup artifacts. By default charts and tables export as individually editable SVG-derived DrawingML shapes, which prioritize cross-app visual consistency. In the default flow, pass `--native-charts-and-tables` to replace eligible groups with PowerPoint-native Chart/Table objects backed by data, which provide **Edit Data** and object-specific controls but may render differently across apps; this variant is saved as `exports/<name>_<timestamp>_native_charts_tables.pptx`. The quick exporter does not accept native-object flags. Both chart/table export variants are editable—the distinction is the PowerPoint object model, not editability itself.
+> **Output:** The SVG pipeline has one PPTX converter: it reads `svg_output/` and writes a directly editable native DrawingML deck to `exports/<name>_<timestamp>.pptx`. The default Generate flow runs `finalize_svg.py` and produces self-contained previews in `svg_final/`; PowerPoint's manual **Convert to Shape** command is outside the supported contract. Explicit [quick generation](./skills/ppt-master/workflows/profiles/quick-generate.md) still converts sources, researches factual gaps, and prepares required images, icons, formulas, and resource manifests when needed. The current agent makes the content, page, visual, and resource decisions in context, skips Strategist, confirmation, `design_spec.md`, `spec_lock.md`, and `finalize_svg.py`, then hand-authors the SVG pages, passes the lockless Quick final quality check, and exports the final PPTX. Ordinary export capabilities remain available as needed, including native chart/table replacement, notes, motion, narration, and diagnostics; notes, custom object animation, and narration start off, and the agent may enable them when the request or deck needs them. A default-path Quick export writes the normal postflight report and snapshots `svg_output/` to `backup/<timestamp>/svg_output/`; an explicit output path keeps the ordinary no-backup behavior. By default charts and tables export as individually editable SVG-derived DrawingML shapes, which prioritize cross-app visual consistency. Pass `--native-charts-and-tables` to replace eligible groups with PowerPoint-native Chart/Table objects backed by data, which provide **Edit Data** and object-specific controls but may render differently across apps; this variant is saved as `exports/<name>_<timestamp>_native_charts_tables.pptx`. Both chart/table export variants are editable—the distinction is the PowerPoint object model, not editability itself.
> **Already have a `.pptx` you want to reuse?** Hand the AI that deck plus your material and ask it to "fill this deck with the new content" — it fills text, table, and chart data into your existing design and exports only the pages you pick, staying natively editable. See the [FAQ](./docs/faq.md) and [template-fill workflow](./skills/ppt-master/workflows/template-fill-pptx.md).
diff --git a/README_CN.md b/README_CN.md
index 7cbd59ff..795fe7a7 100644
--- a/README_CN.md
+++ b/README_CN.md
@@ -325,7 +325,7 @@ AI:好的,先确认设计规范:
AI 全程处理——内容分析、视觉设计、SVG 生成、PPTX 导出。
-> **输出说明:** SVG 管线统一由项目转换器读取 `svg_output/`,生成可直接编辑的原生 DrawingML `.pptx`,保存至 `exports/<name>_<timestamp>.pptx`。默认 Generate 流程会生成自包含预览 `svg_final/`,并把 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`;PowerPoint 手工“转换为形状”不在支持范围。用户可显式启用[快速生成模式](./skills/ppt-master/workflows/profiles/quick-generate.md):仍按需转换来源、研究事实缺口,并准备图片、图标、公式和资源 manifest;当前 Agent 在上下文中自动决定内容、页结构、视觉和资源,跳过 Strategist、确认、`design_spec.md` 与 `spec_lock.md`,随后按规范手写 SVG 并直接导出一个 PPTX,不生成预览、讲稿、验证报告或备份。图表和表格默认导出为 SVG 派生、可逐形状编辑的 DrawingML 对象,优先保证 PowerPoint / Keynote / WPS 间的视觉一致性;默认流程可加 `--native-charts-and-tables`,把符合合同的组替换为带数据源和对象专属编辑能力的 PowerPoint 原生 Chart/Table 对象,跨软件渲染可能略有差异,保存为 `exports/<name>_<timestamp>_native_charts_tables.pptx`;快速导出器不接受原生对象标记。这两种图表/表格导出变体都可编辑,区别在于 PowerPoint 对象模型,而不是“能否编辑”。
+> **输出说明:** SVG 管线统一由项目转换器读取 `svg_output/`,生成可直接编辑的原生 DrawingML `.pptx`,保存至 `exports/<name>_<timestamp>.pptx`。默认 Generate 流程会运行 `finalize_svg.py` 并生成自包含预览 `svg_final/`;PowerPoint 手工“转换为形状”不在支持范围。用户可显式启用[快速生成模式](./skills/ppt-master/workflows/profiles/quick-generate.md):仍按需转换来源、研究事实缺口,并准备图片、图标、公式和资源 manifest;当前 Agent 在上下文中自动决定内容、页结构、视觉和资源,跳过 Strategist、确认、`design_spec.md`、`spec_lock.md` 与 `finalize_svg.py`,随后按规范手写 SVG,通过无锁的 Quick 最终质量检查,再导出最终 PPTX。原生图表 / 表格替换、讲稿、动效、旁白和诊断等普通导出能力仍可按需使用;讲稿、自定义对象动画和旁白默认关闭,Agent 可在用户要求或 deck 确有需要时启用。Quick 使用默认输出路径时仍会生成普通 postflight 报告,并把 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`;显式指定输出路径时沿用普通流程不创建备份的行为。图表和表格默认导出为 SVG 派生、可逐形状编辑的 DrawingML 对象,优先保证 PowerPoint / Keynote / WPS 间的视觉一致性;可加 `--native-charts-and-tables`,把符合合同的组替换为带数据源和对象专属编辑能力的 PowerPoint 原生 Chart/Table 对象,跨软件渲染可能略有差异,保存为 `exports/<name>_<timestamp>_native_charts_tables.pptx`。这两种图表/表格导出变体都可编辑,区别在于 PowerPoint 对象模型,而不是“能否编辑”。
> **已有一份想复用的 `.pptx`?** 把那份 deck 连同素材给 AI,说「套模板」即可——它会把新内容(文字、表格、图表数据)填进你现有的设计,只导出你挑选的页面,且保持原生可编辑。详见 [常见问题](./docs/zh/faq.md) 与 [套模板工作流](./skills/ppt-master/workflows/template-fill-pptx.md)。
diff --git a/docs/faq.md b/docs/faq.md
index b8978160..e046082f 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -77,9 +77,9 @@ Be clear on what this buys you: **web search only finds *a* relevant, downloadab
## Q: Can I edit the generated presentations?
-Yes. The only PPTX converter in the SVG pipeline is PPT Master's own `svg_output/` → DrawingML conversion. It saves a timestamped native PowerPoint deck to `exports/`, with text, graphics, and colors directly editable as PowerPoint objects. In the default Generate flow, a copy of `svg_output/` (the Executor's raw SVG source) is written to `backup/<timestamp>/svg_output/` so you can rebuild via `finalize_svg → svg_to_pptx` without re-running the LLM.
+Yes. The only PPTX converter in the SVG pipeline is PPT Master's own `svg_output/` → DrawingML conversion. It saves a timestamped native PowerPoint deck to `exports/`, with text, graphics, and colors directly editable as PowerPoint objects. With the default output path, both Default Generate and Quick Generate copy the authored `svg_output/` to `backup/<timestamp>/svg_output/`, so the deck can be rebuilt without re-running the LLM.
-`finalize_svg.py` remains a mandatory Step 7 operation in the default Generate flow even though native PPTX export reads `svg_output/`. It produces self-contained files in `svg_final/` for visual inspection and for manual insertion into another deck as SVG pictures. The explicit quick-generate profile skips preview and backup artifacts. PowerPoint's manual **Convert to Shape** command is not a supported round-trip path; use the generated native PPTX when you need editable shapes.
+`finalize_svg.py` remains a mandatory Step 7 operation in the default Generate flow even though native PPTX export reads `svg_output/`. It produces self-contained files in `svg_final/` for visual inspection and for manual insertion into another deck as SVG pictures. The explicit quick-generate profile skips this preview artifact, but still retains the normal postflight report and default-path backup after its lockless final quality check. PowerPoint's manual **Convert to Shape** command is not a supported round-trip path; use the generated native PPTX when you need editable shapes.
## Q: How does multiline text export? Can PowerPoint reflow it?
@@ -208,17 +208,23 @@ Yes. Explicitly request **quick generation**. The Generate route then uses the
source conversion and research for identified factual gaps still run when
needed, but the current agent decides the content, page structure, visual
system, and resource roster in active context without invoking Strategist,
-confirmation, `design_spec.md`, or `spec_lock.md`.
+confirmation, `design_spec.md`, or `spec_lock.md`. It also skips
+`finalize_svg.py`, so Quick creates no `svg_final/` preview.
The profile still prepares every resource the deck needs: supplied or extracted
images, AI/web/sliced images, project icons, rendered formulas, and the required
manifests or provenance records. After preparation, the current agent
-hand-authors `svg_output/` to the shared standards and runs the direct exporter.
-The shortcut still omits structured template reuse, native chart/table
-replacement, Live Preview, visual-review delivery, quality-report files, notes,
-`svg_final/`, backup, animation, and narration. Page count alone neither
-activates nor blocks quick generation. This is a workflow shortcut, not a
-wall-clock or default-quality-equivalence promise.
+hand-authors `svg_output/` to the shared standards, runs the lockless Quick final
+quality checker, fixes every blocking error, and only then exports the final
+PPTX. Ordinary exporter capabilities remain available as needed, including
+native chart/table replacement, notes, motion, narration, and diagnostics.
+Notes, custom object animation, and narration start off; the agent may enable
+them when the request or deck needs them, without opening a confirmation flow.
+A default-path export writes the normal postflight report and snapshots
+`svg_output/` under `backup/`; an explicit output path keeps the ordinary
+no-backup behavior. Page count alone neither activates nor blocks quick
+generation. This is a planning shortcut, not a wall-clock or
+default-quality-equivalence promise.
## Q: Will long decks blow out the context window in one shot?
diff --git a/docs/roadmap.md b/docs/roadmap.md
index 7518589b..561a979c 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -87,8 +87,8 @@ In the cost / speed / quality triangle this project picks **quality**. ~20 minut
Will do: indirect improvements via prompt slimming / cache hit rate.
Explicit `quick-generate` is a user-selected workflow shortcut, not a default
quality-preserving speed optimization: it skips Strategist, confirmation, and
-report-producing quality gates, then authors SVG and exports directly. It makes
-no wall-clock or quality-equivalence promise.
+the first-page gate, then authors SVG, runs one lockless final quality gate, and
+exports the final PPTX. It makes no wall-clock or quality-equivalence promise.
The default Generate pipeline continues to prefer quality over speed.
diff --git a/docs/technical-design.md b/docs/technical-design.md
index 7a598528..75f1ccf5 100644
--- a/docs/technical-design.md
+++ b/docs/technical-design.md
@@ -38,8 +38,9 @@ The three layers have separate responsibilities and cannot substitute for one an
The diagram below covers the default Generate PPTX lifecycle, including its
`beautify-pptx` profile. The explicit `quick-generate` profile stays inside the
-same route but bypasses its separate planning/confirmation and default delivery
-gates; source understanding and resource preparation still run as needed.
+same route but bypasses its separate planning/confirmation, first-page gate,
+and preview finalization. Source understanding and resource preparation still
+run as needed; one lockless final quality gate remains mandatory.
Create Template has its own workspace lifecycle, while Fill Native PPTX and
Enhance Native PPTX operate directly on OOXML; the route table later in this
document covers all four.
@@ -107,6 +108,7 @@ Source material or topic
-> decide content, page structure, visual system, and resources in active context
-> prepare required images/icons/formulas and resource manifests
-> hand-author svg_output/ under the shared SVG standards
+ -> svg_quality_checker.py --quick-generate --stage final --json
-> svg_to_pptx.py --quick-generate
-> exports/<name>_<timestamp>.pptx
```
@@ -117,7 +119,8 @@ Confirm UI, `design_spec.md`, or `spec_lock.md`.
In the default flow, without an explicit `-o`, the native-object and narration
flags may combine into
`<project_name>_<timestamp>_native_charts_tables_narrated.pptx`; explicit `-o`
-preserves the caller-supplied filename. Quick generation accepts neither flag.
+preserves the caller-supplied filename. Quick generation accepts the same
+optional native-object and narration flags.
### SVG as a Constrained Page-Design Language
@@ -157,7 +160,7 @@ Use this table before reasoning about implementation details. Most failed runs s
|---|---|---|
| Topic only, or supplied material lacks facts required by the requested outcome | Generate PPTX + `topic-research` inside Step 1 | topic-only research starts immediately; source-backed research follows conversion/read and fills only identified factual gaps |
| Source files or conversation text, deck structure may be rethought | Generate PPTX | Strategist may split, merge, drop, reorder, and redesign |
-| Explicit quick generation | Generate PPTX + `quick-generate` profile | convert/read sources, research factual gaps, and prepare required resources as needed; the current agent decides content, pages, visuals, and resources in active context, skips Strategist/confirmation/spec/lock, hand-authors SVG, and exports one PPTX directly |
+| Explicit quick generation | Generate PPTX + `quick-generate` profile | convert/read sources, research factual gaps, and prepare required resources as needed; the current agent decides content, pages, visuals, and resources in active context, skips Strategist/confirmation/spec/lock/finalize, hand-authors SVG, passes one lockless final gate, and exports the final PPTX |
| PPTX as source material, user allows a new story/page structure | Generate PPTX via `ppt_to_md` + `pptx_intake` | PPTX identity/geometry are facts and candidates, not replica constraints |
| Raw PPTX template plus new material/topic | Fill Native PPTX (`template-fill-pptx`) | clone/fill native slides; no SVG generation |
| Existing PPTX, preserve page count/order/wording 1:1, improve layout | Generate PPTX + `beautify-pptx` profile | regenerate through SVG; content and pagination are locked |
@@ -188,10 +191,10 @@ Post-processing scripts convert supported SVG vector elements to DrawingML. Text
`quick-generate` retains the source-understanding and resource-preparation work
needed by the deck, but skips the separate Strategist planning/confirmation
-phase and the default report-producing gates. The current agent makes those
+phase, first-page gate, and `finalize_svg.py`. The current agent makes those
content, page, visual, and resource decisions automatically in active context,
-then authors under the shared SVG standards and uses the same DrawingML
-converter, which performs in-memory ZIP and published-Slide-count validation.
+then authors under the shared SVG standards, runs one lockless final quality
+gate, and uses the same DrawingML converter and postflight.
---
@@ -223,7 +226,10 @@ source material or topic
└─> active-context content/page/visual/resource decisions
└─> images/ + icons/ + formula/resource manifests [as needed]
└─> hand-authored svg_output/
- └─> svg_to_pptx.py --quick-generate -> exports/*.pptx
+ └─> svg_quality_checker.py --quick-generate --stage final --json
+ └─> svg_to_pptx.py --quick-generate -> exports/*.pptx
+ + validation/<output_stem>.report.json
+ + backup/<ts>/svg_output/ [default output path]
Direct OOXML routes:
analysis/<stem>.slide_library.json + source PPTX + fill_plan.json
@@ -294,7 +300,7 @@ Two converter design choices still shape the system:
## Project Structure & Lifecycle
-`project_manager.py init` creates the fixed project working directories; a later default export creates a timestamped backup directory and then attempts to copy a `backup/` snapshot. The explicit [`quick-generate`](../skills/ppt-master/workflows/profiles/quick-generate.md) profile omits the planning artifacts and default delivery sidecars, but its project may still contain converted sources, analysis, images, icons, rendered formulas, and required resource manifests. It then hand-authors `svg_output/` and writes the PPTX destination directly. The default delivery lifecycle is:
+`project_manager.py init` creates the fixed project working directories; a later default-path export creates a timestamped backup directory and then attempts to copy a `backup/` snapshot. The explicit [`quick-generate`](../skills/ppt-master/workflows/profiles/quick-generate.md) profile omits planning artifacts and `svg_final/`, but its project may still contain converted sources, analysis, images, icons, rendered formulas, and required resource manifests. It hand-authors `svg_output/`, writes a lockless final quality report, and retains the ordinary postflight and default-path backup around the final PPTX. The default delivery lifecycle is:
| Directory | Role |
|---|---|
@@ -419,7 +425,7 @@ Generate execution is governed by [`workflows/generate-pptx.md`](../skills/ppt-m
Global stop/continue policy is authoritative in [`failure-recovery.md`](../skills/ppt-master/workflows/governance/failure-recovery.md); its concrete recovery matrix and resume pointers currently cover Generate PPTX. This section does not duplicate those rules.
-Three boundaries are especially important to the architecture. First, page SVGs must be hand-authored by the current main agent, one page at a time; writing a Python/Node/shell generator to emit pages is prohibited because the resulting deck loses cross-page judgment and visual continuity. Second, default-pipeline cadence is `P01 → first-page gate → uninterrupted remaining pages → final gate`. P01 is a method sample: execution emits a `gate-signal`, then carries resolved method rules into later pages; no checker call or page batch interrupts P02 through the final page. `quick-generate` retains serial hand-authoring and P01 as its visual anchor but skips both checker gates. Third, routing is deterministic: raw PPTX template requests, beautify-profile requests, native enhancement, custom-animation stages, live-preview stages, and other registered triggers are not turned into open-ended user route questions when the repository already defines the boundary.
+Three boundaries are especially important to the architecture. First, page SVGs must be hand-authored by the current main agent, one page at a time; writing a Python/Node/shell generator to emit pages is prohibited because the resulting deck loses cross-page judgment and visual continuity. Second, default-pipeline cadence is `P01 → first-page gate → uninterrupted remaining pages → final gate`. P01 is a method sample: execution emits a `gate-signal`, then carries resolved method rules into later pages; no checker call or page batch interrupts P02 through the final page. `quick-generate` retains serial hand-authoring and P01 as its visual anchor, skips the first-page gate, and runs one lockless final gate after the complete roster exists. Third, routing is deterministic: raw PPTX template requests, beautify-profile requests, native enhancement, custom-animation stages, live-preview stages, and other registered triggers are not turned into open-ended user route questions when the repository already defines the boundary.
In the default pipeline, the Role Switching Protocol (mandated read of `references/<role>.md` before mode change) serves two reinforcing purposes: forcing fresh role instructions into context overrides drift from the previous mode, and the visible marker in the conversation transcript creates an audit trail so the user can see when the agent moved between modes — critical when reviewing why a particular decision was made.
diff --git a/docs/zh/faq.md b/docs/zh/faq.md
index f43db916..79a72451 100644
--- a/docs/zh/faq.md
+++ b/docs/zh/faq.md
@@ -79,9 +79,9 @@ python3 skills/ppt-master/scripts/update_repo.py
## Q: 生成的 PPT 可以编辑吗?
-可以。SVG 管线统一由项目转换器读取 `svg_output/` 并生成原生 DrawingML `.pptx`;文字、图形和颜色无需额外转换即可编辑,文件以时间戳命名保存至 `exports/`。在默认 Generate 流程中,Executor 的原始 SVG 源(`svg_output/` 副本)会镜像到 `backup/<timestamp>/svg_output/`,便于归档或基于该版重跑 `finalize_svg → svg_to_pptx` 重建 PPTX,无需再走 LLM。
+可以。SVG 管线统一由项目转换器读取 `svg_output/` 并生成原生 DrawingML `.pptx`;文字、图形和颜色无需额外转换即可编辑,文件以时间戳命名保存至 `exports/`。使用默认输出路径时,Default Generate 与 Quick Generate 都会把作者源 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`,便于归档或基于该版重建 PPTX,无需再走 LLM。
-默认 Generate 流程的 Step 7 仍会强制生成 `svg_final/`。其中每页都是自包含的视觉预览 SVG,可直接在浏览器或 IDE 中打开,也可作为 SVG 图片手动插入 PowerPoint;显式快速生成会跳过预览和备份产物。项目只保证 `svg_final/` 作为预览或图片显示,不保证 PowerPoint 手工“转换为形状”后的结果。需要可编辑形状时,请使用 `exports/` 中由项目转换器生成的原生 PPTX。
+默认 Generate 流程的 Step 7 仍会强制生成 `svg_final/`。其中每页都是自包含的视觉预览 SVG,可直接在浏览器或 IDE 中打开,也可作为 SVG 图片手动插入 PowerPoint;显式快速生成会跳过这项预览产物,但在无锁最终质量检查通过后,仍保留普通 postflight 报告和默认输出路径下的备份。项目只保证 `svg_final/` 作为预览或图片显示,不保证 PowerPoint 手工“转换为形状”后的结果。需要可编辑形状时,请使用 `exports/` 中由项目转换器生成的原生 PPTX。
## Q: 多行文本会怎样导出?可以让 PowerPoint 自动重排吗?
@@ -204,9 +204,9 @@ python3 skills/ppt-master/scripts/svg_to_pptx.py <project> -a auto --animation-t
## Q: 可以跳过策略师阶段直接生成吗?
-可以。请显式要求**快速生成**。Generate 路线会启用 [`quick-generate` profile](../../skills/ppt-master/workflows/profiles/quick-generate.md):仍按需转换来源并研究已识别的事实缺口,但当前 Agent 会在上下文中自动决定内容、页结构、视觉系统和资源清单,不进入 Strategist、确认、`design_spec.md` 或 `spec_lock.md`。
+可以。请显式要求**快速生成**。Generate 路线会启用 [`quick-generate` profile](../../skills/ppt-master/workflows/profiles/quick-generate.md):仍按需转换来源并研究已识别的事实缺口,但当前 Agent 会在上下文中自动决定内容、页结构、视觉系统和资源清单,不进入 Strategist、确认、`design_spec.md` 或 `spec_lock.md`;同时跳过 `finalize_svg.py`,因此不生成 `svg_final/` 预览。
-该 profile 仍会按需备齐生成 deck 所需的资源:用户提供或源文件抽取的图片、AI / 网络 / 切片图片、项目图标、渲染公式,以及对应的必要 manifest 或来源记录。备料完成后,当前 Agent 按共享规范手写 `svg_output/`,随后调用直接导出器。短路流程仍不包含结构化模板复用、原生图表 / 表格替换、Live Preview、视觉复核交付、质量报告、讲稿、`svg_final/`、备份、动画或旁白;页数本身既不会自动触发,也不会阻止快速生成。这是工作流短路,不承诺具体耗时,也不承诺与默认流程质量等价。
+该 profile 仍会按需备齐生成 deck 所需的资源:用户提供或源文件抽取的图片、AI / 网络 / 切片图片、项目图标、渲染公式,以及对应的必要 manifest 或来源记录。备料完成后,当前 Agent 按共享规范手写 `svg_output/`,运行无锁的 Quick 最终质量检查并修复所有阻塞错误,之后才导出最终 PPTX。原生图表 / 表格替换、讲稿、动效、旁白和诊断等普通导出能力仍可按需使用;讲稿、自定义对象动画和旁白默认关闭,Agent 可在用户要求或 deck 确有需要时自动启用,不会打开确认流程。使用默认输出路径时会生成普通 postflight 报告,并把 `svg_output/` 备份到 `backup/`;显式指定输出路径时沿用普通流程不创建备份的行为。页数本身既不会自动触发,也不会阻止快速生成。这是规划阶段的短路,不承诺具体耗时,也不承诺与默认流程质量等价。
## Q: 长 PPT 一次生成会不会上下文爆掉?
diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.md
index 61000b2a..55ea65a9 100644
--- a/docs/zh/roadmap.md
+++ b/docs/zh/roadmap.md
@@ -86,7 +86,7 @@ Generate PPTX 路线围绕完全可控的新形状、文字与版式创作。结
会做:通过 prompt 精简 / 缓存命中率提升带来的间接改善。
-显式 `quick-generate` 是用户主动选择的工作流短路,不是默认流程的保质提速:它跳过 Strategist、确认和生成报告的质量门,随后直接创作 SVG 并导出。它不承诺具体耗时,也不承诺与默认流程质量等价。
+显式 `quick-generate` 是用户主动选择的工作流短路,不是默认流程的保质提速:它跳过 Strategist、确认和首屏 gate,随后创作 SVG、运行一次无锁最终质量门,再导出最终 PPTX。它不承诺具体耗时,也不承诺与默认流程质量等价。
默认 Generate 流程仍坚持质量优先。
diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.md
index 91bde3b1..571d4d66 100644
--- a/docs/zh/technical-design.md
+++ b/docs/zh/technical-design.md
@@ -36,7 +36,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使
## Generate PPTX 路线架构
-下图描述 Generate PPTX 的默认生命周期,也包含其 `beautify-pptx` profile。显式 `quick-generate` profile 仍属于同一路线,但只绕过其中独立的规划 / 确认与默认交付门禁;来源理解和资源准备仍按需运行。Create Template 有独立的工作区生命周期;Fill Native PPTX 与 Enhance Native PPTX 直接操作 OOXML。本文后续路线表会覆盖全部四条顶层路线。
+下图描述 Generate PPTX 的默认生命周期,也包含其 `beautify-pptx` profile。显式 `quick-generate` profile 仍属于同一路线,但只绕过独立的规划 / 确认、首屏 gate 与预览终稿化;来源理解和资源准备仍按需运行,一次无锁最终质量门始终保留。Create Template 有独立的工作区生命周期;Fill Native PPTX 与 Enhance Native PPTX 直接操作 OOXML。本文后续路线表会覆盖全部四条顶层路线。
```
用户输入 (PDF/DOCX/XLSX/PPTX/URL/Markdown/主题文本)
@@ -100,6 +100,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使
-> 在当前上下文决定内容、页结构、视觉系统和资源
-> 准备所需图片 / 图标 / 公式与资源 manifest
-> 按共享 SVG 规范手写 svg_output/
+ -> svg_quality_checker.py --quick-generate --stage final --json
-> svg_to_pptx.py --quick-generate
-> exports/<name>_<timestamp>.pptx
```
@@ -109,7 +110,8 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使
默认流程未显式指定 `-o` 时,native 与 narration 标记可以组合成
`<project_name>_<timestamp>_native_charts_tables_narrated.pptx`;显式 `-o`
-则保留调用者给定的文件名。快速生成不接受这两类标记。
+则保留调用者给定的文件名。快速生成同样接受按需启用的 native 与
+narration 标记。
### SVG 是受约束的页面设计语言
@@ -149,7 +151,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使
|---|---|---|
| 只有主题,或现有材料缺少实现用户目标所需的事实 | Generate PPTX Step 1 内运行 `topic-research` | 只有主题时立即研究;有材料时先转换 / 阅读,只补已识别的事实缺口 |
| 有源文件或对话文本,deck 结构可以重想 | Generate PPTX | Strategist 可以拆分、合并、删除、重排和重设计 |
-| 显式要求快速生成 | Generate PPTX + `quick-generate` profile | 按需转换 / 阅读来源、研究事实缺口并准备所需资源;当前 Agent 在上下文中决定内容、页结构、视觉与资源,跳过 Strategist / 确认 / spec / lock,手写 SVG 后直接导出一个 PPTX |
+| 显式要求快速生成 | Generate PPTX + `quick-generate` profile | 按需转换 / 阅读来源、研究事实缺口并准备所需资源;当前 Agent 在上下文中决定内容、页结构、视觉与资源,跳过 Strategist / 确认 / spec / lock / finalize,手写 SVG、通过一次无锁 final gate 后导出最终 PPTX |
| PPTX 作为源材料,用户允许重构故事和页结构 | Generate PPTX,经 `ppt_to_md` + `pptx_intake` | PPTX 身份和几何是事实与候选,不是复刻约束 |
| 原生 PPTX 模板 + 新材料 / 新主题 | Fill Native PPTX(`template-fill-pptx`) | 克隆并填充原生页面;不生成 SVG |
| 现有 PPTX,页数 / 页序 / 措辞 1:1 保留,只改善排版 | Generate PPTX + `beautify-pptx` profile | 通过 SVG 重新生成;内容和分页锁定 |
@@ -178,7 +180,7 @@ Executor 角色逐页生成演示文稿的视觉内容,输出为 SVG 文件。
**第三阶段:工程化转换**
后处理脚本将受支持的 SVG 向量元素转换为 DrawingML。文本和向量形状会保持为 PowerPoint 原生对象——可点击、可编辑、可改样式;位图资源则复制为 PPT picture media,而不是把整页压平成一张图片。
-`quick-generate` 保留 deck 所需的来源理解与资源准备,但跳过独立的 Strategist 规划 / 确认阶段,以及默认流程中生成报告的门禁。当前 Agent 在有效上下文中自动完成内容、页结构、视觉和资源决策,随后仍按共享 SVG 规范创作,并使用同一个 DrawingML 转换器;转换器继续在内存中校验 ZIP 完整性和已发布 Slide 数量。
+`quick-generate` 保留 deck 所需的来源理解与资源准备,但跳过独立的 Strategist 规划 / 确认阶段、首屏 gate 与 `finalize_svg.py`。当前 Agent 在有效上下文中自动完成内容、页结构、视觉和资源决策,随后仍按共享 SVG 规范创作,运行一次无锁最终质量门,并使用同一个 DrawingML 转换器与 postflight。
---
@@ -210,7 +212,10 @@ Quick Generate:
└─> 当前上下文中的内容 / 页结构 / 视觉 / 资源决策
└─> images/ + icons/ + 公式 / 资源 manifest [按需]
└─> 手写 svg_output/
- └─> svg_to_pptx.py --quick-generate -> exports/*.pptx
+ └─> svg_quality_checker.py --quick-generate --stage final --json
+ └─> svg_to_pptx.py --quick-generate -> exports/*.pptx
+ + validation/<output_stem>.report.json
+ + backup/<ts>/svg_output/ [默认输出路径]
直接 OOXML 路由:
analysis/<stem>.slide_library.json + 源 PPTX + fill_plan.json
@@ -281,7 +286,7 @@ SVG 也是唯一同时满足流程中所有角色需要的格式:**AI 能可
## 项目结构与生命周期
-`project_manager.py init` 创建固定的项目工作目录;默认导出随后创建带时间戳的备份目录,再尝试复制 `backup/` 快照。显式 [`quick-generate`](../../skills/ppt-master/workflows/profiles/quick-generate.md) profile 省略规划产物和默认交付 sidecar,但项目中仍可按需存在已转换来源、分析结果、图片、图标、渲染公式及必要资源 manifest;随后手写 `svg_output/` 并直接写入 PPTX 目标。默认交付生命周期如下:
+`project_manager.py init` 创建固定的项目工作目录;使用默认输出路径的导出会创建带时间戳的备份目录,再尝试复制 `backup/` 快照。显式 [`quick-generate`](../../skills/ppt-master/workflows/profiles/quick-generate.md) profile 省略规划产物与 `svg_final/`,但项目中仍可按需存在已转换来源、分析结果、图片、图标、渲染公式及必要资源 manifest;它会手写 `svg_output/`,生成无锁最终质量报告,并围绕最终 PPTX 保留普通 postflight 与默认路径备份。默认交付生命周期如下:
| 目录 | 职责 |
|---|---|
@@ -400,7 +405,7 @@ Generate 执行以 [`workflows/generate-pptx.md`](../../skills/ppt-master/workfl
全路由通用的停止 / 继续规则以 [`failure-recovery.md`](../../skills/ppt-master/workflows/governance/failure-recovery.md) 为准;其中具体故障矩阵与续跑入口目前覆盖 Generate PPTX。本节不复制这些规则。
-其中三条边界尤其关键。第一,页面 SVG 必须由当前主代理逐页手写;禁止写 Python / Node / shell 生成器批量吐 SVG,因为这种输出会丢失跨页判断和视觉连续性。第二,默认流程节奏是 `P01 → first-page gate → 不间断生成其余页面 → final gate`。P01 是方法样本:执行者先输出 `gate-signal`,再把已解决的方法规则带入后续页面;P02 到末页之间不分批,也不插入 checker。`quick-generate` 仍串行手写并以 P01 为视觉锚点,但跳过两道 checker gate。第三,路由是确定性的:原生 PPTX 模板、beautify、native enhancement、自定义动画、live preview 等触发条件已经在仓库里定义清楚时,不再额外抛给用户一个开放式路线选择题。
+其中三条边界尤其关键。第一,页面 SVG 必须由当前主代理逐页手写;禁止写 Python / Node / shell 生成器批量吐 SVG,因为这种输出会丢失跨页判断和视觉连续性。第二,默认流程节奏是 `P01 → first-page gate → 不间断生成其余页面 → final gate`。P01 是方法样本:执行者先输出 `gate-signal`,再把已解决的方法规则带入后续页面;P02 到末页之间不分批,也不插入 checker。`quick-generate` 仍串行手写并以 P01 为视觉锚点,跳过首屏 gate,并在完整 roster 生成后运行一次无锁 final gate。第三,路由是确定性的:原生 PPTX 模板、beautify、native enhancement、自定义动画、live preview 等触发条件已经在仓库里定义清楚时,不再额外抛给用户一个开放式路线选择题。
默认流程的角色切换协议(切换模式前必须 `read_file references/<role>.md`)有两个互相支撑的作用:把新鲜的角色指令载入上下文,覆盖前一模式的漂移;对话 transcript 中的可见标记构成审计轨迹,让用户能看到 agent 何时切换了模式——回看一个具体决策为什么这样做时,这条线索很关键。
diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.md
index 52df0fa5..99d3470a 100644
--- a/skills/ppt-master/references/artifact-ownership.md
+++ b/skills/ppt-master/references/artifact-ownership.md
@@ -9,6 +9,8 @@ profile may explicitly omit an artifact without erasing its facts.
Its current main agent reads source/analysis facts, keeps routine decisions in
active context, and prepares images/icons/formulas plus required manifests
before SVG authoring. Those artifacts retain their factual/provenance roles.
+Quick writes the same final SVG quality provenance and package postflight as
+the default profile, but it does not create `svg_final/`.
---
@@ -46,10 +48,10 @@ before SVG authoring. Those artifacts retain their factual/provenance roles.
| `notes/total.md` | Conditional speaker-note source | Complete notes before splitting | Step 6 writes only when the effective Speaker Notes outcome is enabled; Step 7.1 splits |
| `notes/slide_*.md` | Conditional split notes | Per-slide notes generated from `total.md` | Derived by `total_md_split.py` only when speaker notes are enabled |
| `svg_final/` | Default-only derived visual preview | Self-contained post-processed SVGs that may be opened directly or inserted as SVG pictures | Default rebuilds it from `svg_output/` with `finalize_svg.py`; Quick omits it. Never use it as a supported PPTX source. |
-| `validation/svg_quality_report.json` | Default quality provenance | Final SVG gate split into blocking / introduced / inherited / source-import categories, bound to the checked SVG bytes by SHA-256 | Default `svg_quality_checker.py --stage final --json` writes before export; the exporter links it only when fingerprints match. Quick omits this report. |
-| `validation/<output_stem>.report.json` | Default published-package audit | PPTX package/resource postflight status, part counts, and quality-gate linkage | Default Step 7.3 writes it and emits `[POSTFLIGHT]`; Quick instead performs in-memory package sanity and emits `[QUICK-GENERATE]` without a report. |
+| `validation/svg_quality_report.json` | Final SVG quality provenance | Final SVG gate split into blocking / introduced / inherited / source-import categories, bound to the checked SVG bytes by SHA-256 | Default runs `svg_quality_checker.py --stage final --json`; Quick adds `--quick-generate` so the checker ignores Design Spec/lock and validates the lockless flat roster. Export links the report only when fingerprints match; Quick requires that link to pass before PPTX creation. |
+| `validation/<output_stem>.report.json` | Published-package audit | PPTX package/resource postflight status, part counts, and quality-gate linkage | Both Generate profiles write it and emit `[POSTFLIGHT]` after package validation. |
| `exports/` | Delivery artifacts | Native DrawingML PPTX and explicit native-object/narration variants | Default Step 7.3 or Quick direct export writes final deliverables from `svg_output/`. |
-| `backup/<timestamp>/svg_output/` | Default frozen author-source archive | Re-export source without re-running LLM | Default export writes a snapshot; Quick direct export omits it. |
+| `backup/<timestamp>/svg_output/` | Default-path frozen author-source archive | Re-export source without re-running LLM | Both Generate profiles write a snapshot for default-path exports; explicit `-o/--output` skips it. |
| `animations.json` | Optional animation config | Page-transition and object-animation sidecar | Existing files activate intent resolution: Stage 3 `false` preserves, explicit objects-off exports `-a none`, and all-motion-off bypasses with `--no-animations`. Creation requires explicit instruction or enabled outcome; §IX advice never activates it |
---
@@ -89,8 +91,8 @@ before SVG authoring. Those artifacts retain their factual/provenance roles.
| `<import_workspace>/authoring-svg/authoring_summary.json` | Current authoring SVGs plus tool-only manifest roster | `python3 ${SKILL_DIR}/scripts/svg_authoring_view.py <import_workspace>/authoring-svg --refresh-summary`; in-place vector/picture extraction refreshes it automatically |
| `notes/slide_*.md` | `notes/total.md`, when speaker notes are enabled | `python3 ${SKILL_DIR}/scripts/total_md_split.py <project_path>` |
| `svg_final/` | `svg_output/` plus project assets | `python3 ${SKILL_DIR}/scripts/finalize_svg.py <project_path>` |
-| `validation/svg_quality_report.json` | `svg_output/`, locks, template provenance | `python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage final --json` |
+| `validation/svg_quality_report.json` | `svg_output/`, plus locks/template provenance in Default Generate | Default: `python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> --stage final --json`; Quick: append `--quick-generate` |
| Native PPTX + `validation/<output_stem>.report.json` | `svg_output/` plus notes/assets and final quality report | `python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path>` |
-| Quick native PPTX | `svg_output/` plus prepared project-local resources | `python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-generate` |
+| Quick native PPTX | `svg_output/`, prepared resources, passing Quick final report | `python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-generate` |
**Default - regenerate derived views**: When a source artifact changes, regenerate the derived artifact at the owning step instead of patching the derived file directly.
diff --git a/skills/ppt-master/references/executor-notes.md b/skills/ppt-master/references/executor-notes.md
index 02eadda7..d99752b4 100644
--- a/skills/ppt-master/references/executor-notes.md
+++ b/skills/ppt-master/references/executor-notes.md
@@ -4,11 +4,12 @@
Conditional late-stage authority for generating the complete speaker-notes document.
-**Trigger**: load only after all SVG pages pass the final quality check and the
-effective Speaker Notes outcome in `design_spec.md §I` is enabled. A missing
-legacy outcome uses compatibility default `enabled`; effective Narration Audio
-enabled also requires Speaker Notes enabled. When notes are disabled, do not
-load this branch or create `notes/total.md`.
+**Trigger**: Default Generate loads this after the final quality check when the
+effective Speaker Notes outcome in `design_spec.md §I` is enabled. Quick
+Generate loads it after its final check when the current agent selected notes
+or narration in active context. A missing legacy outcome defaults to enabled.
+Narration requires notes; when notes are disabled, do not load this branch or
+create `notes/total.md`.
## 1. Complete Speaker-notes Document
@@ -16,11 +17,11 @@ Write the complete deck to `notes/total.md` in one batch for coherent transition
**Pure spoken narration**: `notes_to_audio.py` reads the body verbatim. Write prose only; never add Markdown list/bullet markup, stage markers, key-point labels, duration lines, or other metadata.
-**Length follows content**: size natural sentences to semantic burden. Two to five is typical, not a cap; anchor pages may use less and dense pages more. Honor `design_spec.md` style, detail, and source rules. Duration is pacing guidance only: never pad, repeat, compress, or omit meaning to hit it.
+**Length follows content**: size natural sentences to semantic burden. Two to five is typical, not a cap; anchor pages may use less and dense pages more. Honor the active Design Spec or Quick context plus source rules. Duration is pacing guidance only: never pad, repeat, compress, or omit meaning to hit it.
## 2. Final-SVG Grounding and Coverage
-**Hard rule — the final SVG is the visible page authority**: read every finalized `svg_output/<slide>.svg` in slide order. Use the locked plan and approved sources for context; never write from the outline or core message alone.
+**Hard rule — the final SVG is the visible page authority**: read every finalized `svg_output/<slide>.svg` in slide order. Use the active plan/context and approved sources; never write from the outline or core message alone.
Before drafting, internally inventory the visible title/subtitle and every information-bearing direct-root `<g id>`; structured placeholder content still counts. Coverage requires its unique claim, evidence, example, relationship, qualifier, or implication—not merely its label—to enter the narration.
diff --git a/skills/ppt-master/references/image-generator.md b/skills/ppt-master/references/image-generator.md
index 6decc4f2..823072e9 100644
--- a/skills/ppt-master/references/image-generator.md
+++ b/skills/ppt-master/references/image-generator.md
@@ -591,7 +591,7 @@ Triggered automatically when `IMAGE_BACKEND` is not configured (or Path A fails)
- Filenames awaiting manual generation
- Pointer to `images/image_prompts.md` (paste-ready `### Image N:` block per item) or `image_prompts.json` (`items[].prompt`)
- Target placement: `project/images/<filename>` matching the resource list exactly
- - Resume: Default Generate re-runs Step 7; Quick Generate re-runs its resource gate, then `--quick-generate`
+ - Resume: Default Generate re-runs Step 7; Quick Generate re-runs its resource gate, final checker, then `--quick-generate`
**User-initiated**: When Strategist Step 4 captured `manual` in Default Generate, or the user explicitly requested `manual` in the Quick Generate active context, Path A is skipped from the start.
diff --git a/skills/ppt-master/references/svg-image-embedding.md b/skills/ppt-master/references/svg-image-embedding.md
index 50f36105..1b11981b 100644
--- a/skills/ppt-master/references/svg-image-embedding.md
+++ b/skills/ppt-master/references/svg-image-embedding.md
@@ -59,7 +59,7 @@ Each image carries an `Acquire Via` field plus a status annotation. This file is
4. Preview: python3 -m http.server -d <project_path> 8000 → /svg_output/<filename>.svg
5. Export:
- Default Generate → follow [`generate-pptx.md`](../workflows/generate-pptx.md) Step 7
- - Quick Generate → after every required resource has a validated expected file/provenance and a usable status, run the profile's direct `--quick-generate` export
+ - Quick Generate → after every required resource has a validated expected file/provenance and usable status, run the profile's final checker, then its `--quick-generate` export
```
> Keep external references in `svg_output/` during generation. Default Generate uses `finalize_svg.py` to embed images into the mandatory `svg_final/` visual preview. Quick Generate omits that preview artifact. Both native PPTX exports independently read image references from `svg_output/`.
diff --git a/skills/ppt-master/scripts/docs/svg-pipeline.md b/skills/ppt-master/scripts/docs/svg-pipeline.md
index 68a06d5f..74d7b94d 100644
--- a/skills/ppt-master/scripts/docs/svg-pipeline.md
+++ b/skills/ppt-master/scripts/docs/svg-pipeline.md
@@ -252,7 +252,11 @@ for operation, first, second, expected_error in rejections:
assert rejected.returncode != 0
assert expected_error in rejected.stderr, rejected.stderr
-run_tool("svg_quality_checker.py", svg_output, "--format", "ppt169")
+run_tool(
+ "svg_quality_checker.py", project,
+ "--quick-generate", "--format", "ppt169",
+ "--stage", "final", "--json",
+)
pptx = project / "boolean-smoke.pptx"
run_tool("svg_to_pptx.py", project, "--quick-generate", "-o", pptx)
with zipfile.ZipFile(pptx) as archive:
@@ -551,39 +555,40 @@ Explicit direct generation may use the
current agent has converted/read sources, researched identified factual gaps,
and prepared the required images, icons, formulas, and resource manifests as
needed. That profile skips Strategist, Confirm UI, `design_spec.md`, and
-`spec_lock.md`; it does not skip the resources required by the authored pages:
+`spec_lock.md`; it does not skip the resources required by the authored pages.
+After the complete SVG roster exists, run its lockless final checker, then
+export:
```bash
+python3 scripts/svg_quality_checker.py <project_path> \
+ --quick-generate --stage final --json
python3 scripts/svg_to_pptx.py <project_path> --quick-generate
```
This direct-export flag takes `svg_output/` as its authored page source, resolves
valid project-local resources referenced by those pages, infers one consistent
-canvas, uses flat converter-default package scaffolding, disables notes and
-motion, and does not read or require `spec_lock.md`. The exporter itself writes
-the PPTX only: no `backup/`, conversion trace, or `validation/` report. Existing
-source, analysis, image/icon/formula, and resource-manifest artifacts are
-allowed and remain untouched. ZIP integrity and Slide count are checked in
-memory; non-quiet runs report
-`[QUICK-GENERATE] status=passed`. The flag rejects options that would add native
-data objects, motion, narration, alternate SVG sources, or export diagnostic
-sidecars.
-The receipt proves only ZIP integrity and equality between discovered SVG and
-published Slide counts; it is not an SVG-quality, visual, factual, or normal
-postflight approval.
+canvas, uses flat converter-default package scaffolding, and does not read or
+require `spec_lock.md`. Notes, motion, narration, native objects, conversion
+trace, and other ordinary exporter capabilities remain available; notes,
+custom object animation, and narration start off in Quick and may be enabled
+when needed. The exporter refuses a missing, blocking, non-final, or stale
+Quick final report before PPTX creation. Default-path output retains the normal
+postflight report and `backup/` snapshot; explicit `-o` retains the ordinary
+no-backup behavior. Existing source, analysis, image/icon/formula, and
+resource-manifest artifacts remain untouched.
For generated-project narration, follow the
[`generate-audio`](../../workflows/stages/generate-audio.md) stage. It owns voice
selection, audio generation, and the narrated re-export workflow.
Behavior:
-- Default output (default Generate flow, no `-o`):
+- Default output (either Generate profile, no `-o`):
- `exports/<project_name>_<timestamp>.pptx` — native editable pptx (canonical output)
- `validation/<project_name>_<timestamp>.report.json` — package postflight, quality-gate linkage, unresolved resource audit, and published part counts
- - `backup/<timestamp>/svg_output/` — copy of Executor SVG source, always written so the pptx can be rebuilt via `finalize_svg → svg_to_pptx` without re-running the LLM
+ - `backup/<timestamp>/svg_output/` — copy of authored SVG source for re-export without re-running the LLM
- `exports/` contains only final PPTX deliverables; machine-readable quality and postflight reports belong in `validation/`.
- The default Generate flow always runs `finalize_svg.py` before export. This directory is the self-contained SVG visual preview; it is not packaged as a second PPTX. Quick-generate deliberately skips it.
-- In the default Generate flow, explicit `-o/--output` changes the native PPTX destination and skips `backup/`; its postflight report still uses the output stem under the project `validation/` directory. Quick-generate writes no report.
+- In both Generate profiles, explicit `-o/--output` changes the native PPTX destination and skips `backup/`; the postflight report still uses the output stem under the project `validation/` directory.
- Postflight reruns ZIP integrity and published Slide count. Internal relationships,
structured-package validation, transitions, and animations are enforced before the
builder publishes the PPTX and are reported as `enforced-at-build`, not as repeated
@@ -619,14 +624,14 @@ Behavior:
- `[Content_Types].xml` is generated from the actual media extensions written into the PPTX. Unknown media extensions fail unless Python's `mimetypes` can identify them.
- Native export writes to a temporary file first and publishes the requested PPTX only after conversion succeeds. A failed conversion does not replace the main output file.
- `--conversion-trace` without a path writes `validation/<output_stem>.trace.json`. `--conversion-trace <path>` respects the explicit destination; relative paths are resolved from the project root, so `exports/<name>.trace.json` remains available when intentionally requested.
-- After normal-flow publication, native export writes `validation/<output_stem>.report.json`. The report distinguishes authored Slides from internal Layout definitions, reruns ZIP integrity and published Slide-count checks, records slide/layout/master/notes part counts, labels relationship/structured/transition/animation validation as enforced at build time, links the final SVG quality report only when its SHA-256 source fingerprint matches the exact export inputs, and surfaces stale/unverified gates, unresolved template tokens, generic-only font stacks, and external image references. A matching final quality report with introduced warnings yields `passed-with-warnings` and a `quality_introduced_warnings=<N>` receipt instead of a clean `passed` claim.
+- After publication, native export writes `validation/<output_stem>.report.json`. The report distinguishes authored Slides from internal Layout definitions, reruns ZIP integrity and published Slide-count checks, records slide/layout/master/notes part counts, labels relationship/structured/transition/animation validation as enforced at build time, links the final SVG quality report only when its SHA-256 source fingerprint matches the exact export inputs, and surfaces stale/unverified gates, unresolved template tokens, generic-only font stacks, and external image references. A matching final quality report with introduced warnings yields `passed-with-warnings` and a `quality_introduced_warnings=<N>` receipt instead of a clean `passed` claim.
- By default, a successful command also prints a compact receipt instead of requiring a report read: `[POSTFLIGHT] status=<...> quality_gate=<...> slides=<N> warning_categories=<N>`, followed by one compact line per warning category and the `[PPTX]` / `[REPORT]` paths. Resource-warning lines carry counts; a non-passing quality gate carries its status. Routine agents use this receipt and do not load either complete validation JSON into model context. Full reports remain cold audit artifacts; failure investigation and explicit audits extract only the required fields. `--quiet` keeps suppressing successful-run output.
- Before publishing structured template output, export reopens the temporary PPTX and validates the Slide → Layout → Master graph and registrations, Layout identity, placeholder identity, reusable bounds, and prompt/level-one sizes. A mismatch aborts publication. Flat release instead validates its single referenced Master/Layout shell and exact date/footer/slide-number hook roster before packaging.
- Authored SVG clip-path restrictions remain. Crop wrappers use an
overflow-hidden viewport; preview-safe shape clips target the inner image in
viewBox coordinates, while legacy imported wrapper clips remain compatible.
Both map to native picture crop/geometry when possible.
-- The default Generate flow embeds speaker notes automatically unless `--no-notes` is used; quick-generate always disables them
+- The default Generate flow embeds speaker notes automatically unless `--no-notes` is used; Quick Generate defaults them off and enables them with `--with-notes`
- Recorded narration is opt-in:
- `notes_to_audio.py` uses `edge-tts` by default, or a configured cloud TTS provider (`elevenlabs`, `minimax`, `qwen`, `cosyvoice`), and generates one audio file per slide into `audio/`
- Narration text is read strictly from the matching `notes/*.md` file; the script only skips Markdown heading lines (`# ...`) and does not summarize, rewrite, or filter delivery notes
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index 1e987741..58c6ce9a 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -12,7 +12,7 @@
"skills/ppt-master/templates/schemas/*.json"
],
"exclude": [],
- "max_tokens": 400200
+ "max_tokens": 400600
},
"file_budgets": {
"AGENTS.md": 2400,
@@ -33,7 +33,7 @@
"skills/ppt-master/references/strategist-template.md": 2100,
"skills/ppt-master/templates/design_spec_reference.md": 3275,
"skills/ppt-master/templates/spec_lock_reference.md": 2375,
- "skills/ppt-master/workflows/generate-pptx.md": 13825,
+ "skills/ppt-master/workflows/generate-pptx.md": 13850,
"skills/ppt-master/workflows/stages/apply-template-workspace.md": 1800
},
"load_sets": {
@@ -93,7 +93,7 @@
"skills/ppt-master/templates/README.md",
"skills/ppt-master/templates/decks/README.md"
],
- "max_tokens": 58300
+ "max_tokens": 58325
},
"route.create-template.layout": {
"description": "Create Layout path through Template_Designer, SVG core, and the structured PPTX interface.",
@@ -111,7 +111,7 @@
"skills/ppt-master/templates/README.md",
"skills/ppt-master/templates/layouts/README.md"
],
- "max_tokens": 58475
+ "max_tokens": 58500
},
"route.enhance-native-pptx": {
"description": "Finished-PPTX native enhancement route.",
@@ -122,7 +122,7 @@
"files": [
"skills/ppt-master/workflows/native-enhance-pptx.md"
],
- "max_tokens": 9750
+ "max_tokens": 9775
},
"route.fill-native-pptx": {
"description": "Raw-PPTX native fill route.",
@@ -133,7 +133,7 @@
"files": [
"skills/ppt-master/workflows/template-fill-pptx.md"
],
- "max_tokens": 11450
+ "max_tokens": 11475
},
"route.generate.planning": {
"description": "Generate-PPTX planning through Strategist, including reference-first whole-document authoring and representative multi-source custom mode/style synthesis; schemas and optional scaffolds are tool-consumed.",
@@ -170,7 +170,7 @@
"registry": "visual-styles"
}
],
- "max_tokens": 62225
+ "max_tokens": 62325
},
"route.generate.quick-generate": {
"description": "Explicit non-interactive Generate path with conditional source/resource preparation and the shared SVG authoring core.",
@@ -184,7 +184,7 @@
"skills/ppt-master/references/artifact-ownership.md",
"skills/ppt-master/references/shared-standards-core.md"
],
- "max_tokens": 36650
+ "max_tokens": 36950
},
"route.generate.quick-generate.topic-research": {
"description": "Quick Generate with gap-targeted factual research before direct resource preparation and SVG authoring.",
@@ -194,7 +194,7 @@
"stage.generate.topic-research"
],
"files": [],
- "max_tokens": 38150
+ "max_tokens": 38450
},
"route.generate.quick-generate.icon": {
"description": "Quick Generate with project-local bundled icon selection and synchronization.",
@@ -205,7 +205,7 @@
"files": [
"skills/ppt-master/templates/icons/README.md"
],
- "max_tokens": 38550
+ "max_tokens": 38850
},
"route.generate.quick-generate.in-hand-image": {
"description": "Quick Generate with supplied, extracted, or placeholder image resources prepared before SVG authoring.",
@@ -215,7 +215,7 @@
"stage.generate.executor.image"
],
"files": [],
- "max_tokens": 43675
+ "max_tokens": 43975
},
"route.generate.quick-generate.formula": {
"description": "Quick Generate with manifest-driven formula rendering and formula-image realization.",
@@ -227,7 +227,7 @@
"files": [
"skills/ppt-master/scripts/docs/image.md"
],
- "max_tokens": 46850
+ "max_tokens": 47150
},
"route.generate.quick-generate.ai-two-types": {
"description": "Quick Generate with AI resource preparation, representative rendering inputs, and two local image types.",
@@ -238,7 +238,7 @@
"stage.generate.executor.image"
],
"files": [],
- "max_tokens": 66700
+ "max_tokens": 67000
},
"route.generate.quick-generate.web-image": {
"description": "Quick Generate with web resource preparation, provenance, attribution, and image execution.",
@@ -249,7 +249,7 @@
"stage.generate.executor.web-image"
],
"files": [],
- "max_tokens": 51425
+ "max_tokens": 51725
},
"route.generate.planning-image": {
"description": "Generate-PPTX planning context after a non-none image source is proposed or confirmed; layout-catalog recall remains optional.",
@@ -269,7 +269,7 @@
"stage.generate.strategist.image"
],
"files": [],
- "max_tokens": 64750
+ "max_tokens": 64850
},
"route.generate.planning-ai": {
"description": "Generate-PPTX planning when AI image direction is available, including representative multi-source custom rendering synthesis.",
@@ -401,7 +401,7 @@
"stage.generate.executor.notes"
],
"files": [],
- "max_tokens": 87900
+ "max_tokens": 88025
},
"route.generate.flat-ai-two-types": {
"description": "Generate-PPTX context with AI images, representative multi-source custom rendering, and two local types.",
@@ -459,7 +459,7 @@
"profile.generate.beautify-pptx"
],
"files": [],
- "max_tokens": 94825
+ "max_tokens": 94950
},
"route.generate.flat-no-image-chart": {
"description": "Default flat Generate-PPTX path with chart authoring, native-data replacement, and verification.",
@@ -472,7 +472,7 @@
"stage.generate.verify-charts"
],
"files": [],
- "max_tokens": 112225
+ "max_tokens": 112350
},
"route.generate.brand-flat-no-image": {
"description": "Brand-preset flat Generate-PPTX path without image acquisition.",
@@ -484,7 +484,7 @@
"stage.generate.template.brand"
],
"files": [],
- "max_tokens": 94925
+ "max_tokens": 95050
},
"route.generate.deck-structured-no-image": {
"description": "Deck-preset structured Generate-PPTX path without image acquisition.",
@@ -496,7 +496,7 @@
"stage.generate.template.deck"
],
"files": [],
- "max_tokens": 104875
+ "max_tokens": 105000
},
"route.generate.layout-structured-no-image": {
"description": "Layout-preset structured Generate-PPTX path without image acquisition.",
@@ -508,7 +508,7 @@
"stage.generate.template.layout"
],
"files": [],
- "max_tokens": 105325
+ "max_tokens": 105425
},
"route.generate.topic-only-flat-no-image": {
"description": "Topic research followed by the default flat no-image Generate-PPTX path.",
@@ -518,7 +518,7 @@
"route.generate.flat-no-image"
],
"files": [],
- "max_tokens": 89400
+ "max_tokens": 89525
},
"stage.generate.executor.flat": {
"description": "Incremental flat Executor core with representative multi-source custom mode/style execution.",
@@ -618,7 +618,7 @@
"skills/ppt-master/workflows/stages/resume-execute.md",
"skills/ppt-master/references/artifact-ownership.md"
],
- "max_tokens": 51000
+ "max_tokens": 51025
},
"stage.generate.resume-execute-image": {
"description": "Fresh-session resume when the locked resource plan contains image rows.",
@@ -698,7 +698,7 @@
"skills/ppt-master/scripts/docs/pptx-transitions.md",
"skills/ppt-master/scripts/docs/svg-pipeline.md"
],
- "max_tokens": 28975
+ "max_tokens": 29025
},
"stage.generate.video-motion-plan": {
"description": "Conditional resolved animation-to-video handoff contract.",
@@ -764,7 +764,7 @@
"stage.generate.strategist.template"
],
"files": [],
- "max_tokens": 64300
+ "max_tokens": 64400
},
"route.generate.planning-template-ai": {
"description": "Explicit template workspace plus confirmed AI-image planning.",
diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.md
index 0832fe1b..c9fa2ff2 100644
--- a/skills/ppt-master/workflows/generate-pptx.md
+++ b/skills/ppt-master/workflows/generate-pptx.md
@@ -21,14 +21,15 @@ For an explicit quick/fast, skip-strategy, or direct-SVG request, follow
[`quick-generate.md`](./profiles/quick-generate.md). It runs applicable source
conversion/research and project-local resource preparation, lets the current
agent decide content/visual/resource details in active context, then
-hand-authors SVG and exports directly. It invokes no Strategist, Confirm UI,
-Design Spec refinement, or lock authoring.
+hand-authors SVG, runs one lockless final checker, and exports the final PPTX.
+It skips Strategist, Confirm UI, Design Spec/lock, the first-page gate, and
+`finalize_svg.py`.
**Hard rule — no implicit downgrade or page cap**: page count neither selects
nor blocks quick generation. Source preparation, images, icons, formulas, and
-their manifests remain valid. Structured template reuse, native data objects,
-Live Preview, notes, motion, narration, or visual-review delivery requires the
-default pipeline; do not silently drop those requested capabilities.
+their manifests remain valid. All exporter capabilities remain available when
+requested or agent-selected; use their existing prerequisites. Structured
+template reuse still requires the default lock-backed pipeline.
### SVG Page-Design Boundary
diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.md
index 2b3a3175..e2d3efd4 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -1,12 +1,12 @@
---
-description: Generate profile for agent-decided source and resource preparation, direct SVG authoring, and one PPTX export without Strategist or confirmation artifacts.
+description: Generate profile for agent-decided source and resource preparation, direct SVG authoring, and final PPTX delivery without Strategist or confirmation artifacts.
---
# Quick Generate Profile
> Generate-PPTX profile, not a top-level route. It removes the separate
-> Strategist and confirmation phase; it does not remove the facts or visible
-> resources needed to build the deck.
+> Strategist and confirmation phase; it does not remove the facts, resources,
+> or export capabilities needed to build the final deck.
**Trigger**: the user explicitly requests quick/fast generation, asks to skip
strategy/confirmation, or directs the agent to proceed to SVG and export.
@@ -18,31 +18,32 @@ Page count alone never activates or blocks this profile.
| Concern | Quick Generate contract |
|---|---|
-| Interaction | The current main agent resolves routine content, page, visual, and resource choices in active context; do not invoke Strategist, open Confirm UI, or wait for design confirmation |
+| Interaction | The current main agent decides content, design, resources, and implementation without Strategist, Confirm UI, or approval stops |
| Inputs | Any supported Generate input; convert/import sources and run bounded factual research when the input requires them |
| Resources | Prepare every project-local image, icon, formula, and required provenance/manifest artifact before the referencing SVG is authored |
| Planning artifacts | Do not create `design_spec.md`, `spec_lock.md`, confirmation payloads, or a second persisted strategy |
-| Delivery | Hand-author the resolved SVG roster and export one native PPTX through `--quick-generate` |
+| Delivery | Hand-author the resolved SVG roster, run one lockless final checker, skip `finalize_svg.py`, and export the final native PPTX through `--quick-generate` |
**Hard rule — speed removes interaction, not material**: source conversion,
topic research, supplied/extracted assets, AI or web images, illustration
slices, project icons, formula rendering, and regenerated image facts remain
available whenever the deck needs them. The workspace may therefore contain
`sources/`, `analysis/`, `images/`, `icons/`, and their operational manifests.
-Do not misread direct export's lack of report sidecars as a ban on resource
-artifacts.
+The missing planning contract relaxes design constraints; it does not remove
+resource preparation or exporter capabilities.
Explicit user facts, wording, choices, exclusions, and permission boundaries
still win. For every unspecified routine choice, decide directly and continue;
-do not ask the user to approve a provisional strategy. Stop only when a required
-fact/resource cannot be resolved safely or an explicit user decision is
-genuinely required.
+do not ask the user to approve a strategy or implementation detail.
-Structured template reuse, native chart/table replacement, Live Preview,
-speaker notes, animation, narration, and visual-review delivery remain
-default-pipeline capabilities. Do not silently discard one of those requested
-capabilities to fit this profile. Source preparation and visible-page resource
-preparation do not disqualify Quick Generate.
+After entry, continue through selected work, the final checker, and export.
+Pause only for user interruption or an unresolved hard prerequisite.
+
+**Default — optional production behavior (may override when useful)**: Speaker
+notes, custom object animations, and narration start off. The current agent may
+enable any ordinary capability when the request or deck benefits; use its
+normal inputs, flags, and prerequisites without asking for approval. Quick
+never creates or reads a Design Spec or lock to enable it.
---
@@ -52,8 +53,8 @@ Run [`generate-pptx.md`](../generate-pptx.md) Step 1 source conversion and
bounded research when applicable. Initialize/import the project through Step 2
when those tools or project-local resources are needed, but never scaffold a
Design Spec or lock. Use a new project path, or first verify that its
-`svg_output/` is empty and that no `design_spec.md` / `spec_lock.md` from
-another pipeline is present.
+`svg_output/` is empty; Quick does not read any existing `design_spec.md` or
+`spec_lock.md`.
Before writing P01, resolve in active context:
@@ -98,7 +99,7 @@ Always read
[`shared-standards-core.md`](../../references/shared-standards-core.md). Do not
load `executor-base.md`: its persisted-plan prerequisites do not apply to this
profile. Load the conditional image/web/canvas references only when the
-resolved SVG needs them.
+resolved SVG or selected capability needs them.
Use one zero-padded filename width sized for the resolved roster, such as
`01_cover.svg` through `12_end.svg` or `001_cover.svg` through `120_end.svg`.
@@ -120,17 +121,24 @@ and omit Master/Layout/layer/placeholder metadata.
on a lock or generated font asset.
**Generation pacing**: the current main agent hand-writes the SVG roster in
-order. Use P01 as the visual anchor, continue directly through the remaining
-pages, and skip the default first-page and final checker gates. This profile
-still obeys every loaded SVG/resource rule; skipping a report does not relax
-the authoring contract.
+order. Use P01 as the visual anchor and continue directly through the remaining
+pages without a first-page checker or confirmation stop. After the complete
+roster exists, run the one final checker below. Apply other supporting tools
+and stages only when their capability is actually needed.
---
-## 4. Direct Export
+## 4. Export
+
+After every page and required referenced resource exists, run the lockless
+final SVG check:
+
+```bash
+python3 ${SKILL_DIR}/scripts/svg_quality_checker.py <project_path> \
+ --quick-generate --stage final --json
+```
-Run one export command after every page exists and every required referenced
-resource in the resolved roster has validated evidence and a usable status:
+Fix every blocking error and rerun the same command. Then export:
```bash
python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-generate
@@ -138,23 +146,25 @@ python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-generate
`--quick-generate` reads `svg_output/` as the page source and resolves the
project-local assets referenced by those SVGs. It infers one consistent canvas,
-uses a flat PowerPoint package with converter defaults, disables notes and
-motion, skips lock/theme export sidecars, and writes no backup, conversion
-trace, or validation report. Resource manifests remain in the project. An
-explicit `-o <path>.pptx` may replace the default `exports/` destination.
-
-**Package sanity**: the standard non-quiet command succeeds only when
-`[QUICK-GENERATE] status=passed`, the discovered SVG count equals the published
-Slide count, and the PPTX passes in-memory ZIP integrity. This receipt does not
-claim SVG-checker, visual-quality, factual-correctness, or default postflight
-approval. On failure, repair the owning SVG/resource and rerun this command; do
-not create planning or validation-report artifacts.
+uses a lockless flat PowerPoint package, and does not force-disable ordinary
+export options. Notes, custom object animation, and narration remain off unless
+selected by the agent. Do not run `finalize_svg.py`.
+
+The exporter requires a passing `final` report whose SVG fingerprint matches
+the current `svg_output/`; missing, blocking, non-final, or stale reports stop
+before PPTX creation. The default output path retains ordinary backup and
+postflight behavior. An explicit `-o <path>.pptx` keeps the ordinary no-backup
+behavior. On failure, repair the owning SVG, resource, or optional capability
+input, rerun the final checker, then export again; do not create a Design Spec
+or lock.
```markdown
## ✅ Quick Generate Complete
- [x] All required source/resource preparation is complete
- [x] Resolved SVG pages and their project-local references exist
+- [x] The lockless final SVG quality report passes and matches the current SVGs
+- [x] Every selected optional export capability completed
- [x] One native PPTX exists under `exports/` or the explicit output path
- [x] No Strategist, confirmation, Design Spec, or lock artifact was created
- [ ] **Next**: Report the PPTX path
diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.md
index 1654cadd..ab47723f 100644
--- a/skills/ppt-master/workflows/routing.md
+++ b/skills/ppt-master/workflows/routing.md
@@ -41,7 +41,7 @@ route selection. After selection, the route authority owns execution.
| Request condition | Generate-route behavior |
|---|---|
-| Explicit quick/fast, skip-strategy, or direct SVG-to-PPTX intent | Activate [`quick-generate`](./profiles/quick-generate.md): prepare sources/resources as needed, let the current agent decide without interaction, omit Strategist/confirmation, hand-author SVG, and export directly |
+| Explicit quick/fast, skip-strategy, or direct SVG-to-PPTX intent | Activate [`quick-generate`](./profiles/quick-generate.md): prepare sources/resources as needed, let the current agent decide without interaction, omit Strategist/confirmation/spec/lock, hand-author SVG, run the lockless final checker, and export the final PPTX |
| Topic only, or supplied sources leave planning-critical factual gaps | Run [`topic-research`](./stages/topic-research.md) inside the selected Generate profile's source preparation: immediately for topic-only input, or after conversion and reading for source-backed input; research only the identified gaps |
| Existing PPTX may be split, merged, dropped, reordered, or re-outlined | Treat the PPTX as source content through [`generate-pptx`](./generate-pptx.md) Step 1 and its PPTX intake; continue the default pipeline unless explicit Quick Generate intent selected that profile |
| Existing PPTX must preserve wording, page count, and page order 1:1 | Activate the [`beautify-pptx`](./profiles/beautify-pptx.md) profile inside the main pipeline |
@@ -61,9 +61,9 @@ route selection. After selection, the route authority owns execution.
**Hard rule — direct-generation profile, not a fifth route**: `quick-generate`
stays inside Generate PPTX but owns an explicit SVG → PPTX short circuit. Page
count alone never activates or blocks it. Conversion, bounded research, and
-project-local image/icon/formula preparation remain available. Structured
-template reuse, native data objects, or additional package behavior require the
-default Generate pipeline.
+project-local resources remain available. Package capabilities may be requested
+or agent-selected. Structured template reuse requires the default lock-backed
+Generate pipeline.
---
diff --git a/skills/ppt-master/workflows/stages/customize-animations.md b/skills/ppt-master/workflows/stages/customize-animations.md
index 1e25a35e..622fa967 100644
--- a/skills/ppt-master/workflows/stages/customize-animations.md
+++ b/skills/ppt-master/workflows/stages/customize-animations.md
@@ -11,7 +11,9 @@ description: Optional post-processing stage for per-slide and per-object animati
> outcome in `design_spec.md §I` is enabled. Deck-wide transitions,
> auto-advance, and deck-wide per-element settings without page-specific motion
> or an existing sidecar use [`animations.md`](../../references/animations.md)
-> directly and do not activate this stage.
+> directly and do not activate this stage. In Quick Generate, the current agent
+> may activate either path from the request/deck in active context without a
+> Design Spec or user interaction.
## When to Run
@@ -52,7 +54,7 @@ sidecars enter this stage; explicit disables follow the table without deletion.
| Explicit adjustment / tuning / repair | Validate first, preserve the existing choreography where its semantic units remain valid, and migrate affected group references after any required regrouping |
| Stage activated with an existing sidecar and new §IX suggestions but no user replacement request | Validate first; preserve valid existing choreography and adjust only the affected semantic units |
| Existing sidecar with no new motion instruction | Validate and preserve it unchanged; if invalid, repair the owning sidecar/group reference before export |
-| Ambiguous generation request | Ask whether to regenerate from scratch or modify the current animation; do not choose on the user's behalf |
+| Ambiguous generation request | Default Generate asks whether to regenerate or modify; Quick Generate decides from the request, visible SVG, and existing sidecar, then continues |
Unless explicit all-motion disable bypasses it, validate an existing sidecar
before deciding to preserve, modify, or suppress object motion:
diff --git a/skills/ppt-master/workflows/stages/generate-audio.md b/skills/ppt-master/workflows/stages/generate-audio.md
index a0b93311..d4f70b78 100644
--- a/skills/ppt-master/workflows/stages/generate-audio.md
+++ b/skills/ppt-master/workflows/stages/generate-audio.md
@@ -10,15 +10,17 @@ This stage is **context-independent**: it reads `notes/*.md` and queries the sel
**Trigger**: In Generate PPTX, run when the effective `Narration Audio` outcome
in `design_spec.md` §I is `enabled`; a later explicit request first updates that
-outcome and its provenance. In Enhance Native PPTX, run when its confirmed
-enhancement plan has `audio.enabled: true`.
+outcome and its provenance. Quick Generate instead runs when the request or
+current agent's active-context decision selects narration. In Enhance Native
+PPTX, run when its confirmed enhancement plan has `audio.enabled: true`.
**Hard dependency — speaker notes**: Audio requires complete per-slide speaker
notes. Generate PPTX additionally requires its effective `Speaker Notes`
outcome to be enabled; Enhance Native PPTX follows its confirmed notes/audio
-plan, where enabling audio also enables notes. Do not enter audio generation
-while the owning route's notes are missing or incomplete; generate and validate
-those notes first, then resume this stage.
+plan, where enabling audio also enables notes. Quick records the same dependency
+in active context. Do not enter audio generation while the owning route's notes
+are missing or incomplete; generate and validate those notes first, then resume
+this stage.
## When to Run
@@ -56,7 +58,7 @@ The AI already knows the deck's language from writing the notes. No detection sc
- Identify the primary language from the notes content: `zh` / `en` / `ja` / `ko` / etc.
- For mixed-language decks (e.g. Chinese with English technical terms), pick the language the audience will hear most of.
-- For Chinese specifically: pick the locale based on context — `zh-CN` (mainland mandarin, default), `zh-TW` (Taiwanese mandarin), or `zh-HK` (Cantonese). Ask the user only if the project context doesn't make it clear.
+- For Chinese specifically: pick the locale based on context — `zh-CN` (mainland mandarin, default), `zh-TW` (Taiwanese mandarin), or `zh-HK` (Cantonese). Default Generate may ask when context is unclear; Quick chooses the best supported default and continues.
---