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(generate): define direct quick-generation workflow
hugohe3310666b615c3
diff --git a/AGENTS.md b/AGENTS.mdindex d553c145..7e950b7c 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -6,14 +6,14 @@ This file is the project entry point for general AI agents.## Project Overview-PPT Master is an AI-driven presentation generation system. Multi-role collaboration (Strategist → Image_Generator → Executor) converts source documents (PDF/DOCX/URL/Markdown) into natively editable PPTX with real PowerPoint shapes (DrawingML). The Generate route owns its pipeline sequence.+PPT Master turns source material into natively editable DrawingML PPTX. Generate owns a default Strategist → Image_Generator → Executor pipeline and an explicit quick-generation bypass.**Route selection authority**: [`skills/ppt-master/workflows/routing.md`](skills/ppt-master/workflows/routing.md) owns the four top-level artifact routes: Generate PPTX, Create Template, Fill Native PPTX, and Enhance Native PPTX. Child workflows, profiles, stages, and governance documents refine one selected route; they are not competing top-level routes.- 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 disposable tests with a small fixed roster of self-contained slides may use the Generate-route [`quick-test`](skills/ppt-master/workflows/profiles/quick-test.md) profile: hand-author `svg_output/` and run the test-only direct exporter, producing no normal planning, preview, notes, validation, or backup artifacts.+- Explicit quick/fast generation from fact-sufficient self-contained content may use [`quick-generate`](skills/ppt-master/workflows/profiles/quick-generate.md): decide structure in context, skip Strategist/confirmation, hand-author `svg_output/`, and export directly without default sidecars.- 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.mdindex 14a77641..133e16e2 100644--- a/README.md+++ b/README.md@@ -303,7 +303,8 @@ You: Please create a PPT from projects/q3-report/sources/report.pdfYou: Please turn the following into a PPT: [paste your content here...]```-Either way, the AI will first confirm the design spec:+By default—unless you explicitly request quick generation—the AI first confirms+the design spec:```AI: Sure. Let's confirm the design spec:@@ -315,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 normal delivery 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 disposable few-page tests may instead use [quick-test mode](./skills/ppt-master/workflows/profiles/quick-test.md), which writes only the authored SVGs and one PPTX—no planning, preview, notes, validation, or backup artifacts. 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 routes 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`, 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 from fact-sufficient self-contained content may instead use [quick-generate mode](./skills/ppt-master/workflows/profiles/quick-generate.md): the agent decides the page structure in active context, skips Strategist and confirmation, writes 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. 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.mdindex 68647095..67d530b9 100644--- a/README_CN.md+++ b/README_CN.md@@ -313,7 +313,7 @@ pip install -r requirements.txt你:请根据以下内容制作成 PPT:[粘贴你的文字内容...]```-两种方式下 AI 都会先确认设计规范:+默认流程下(除非显式要求快速生成),AI 会先确认设计规范:```AI:好的,先确认设计规范:@@ -325,7 +325,7 @@ AI:好的,先确认设计规范:AI 全程处理——内容分析、视觉设计、SVG 生成、PPTX 导出。-> **输出说明:** SVG 管线统一由项目转换器读取 `svg_output/`,生成可直接编辑的原生 DrawingML `.pptx`,保存至 `exports/<name>_<timestamp>.pptx`。正式交付流程会生成自包含预览 `svg_final/`,并把 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`;PowerPoint 手工“转换为形状”不在支持范围。明确用于临时测试的少量自包含页面可改用[快速测试模式](./skills/ppt-master/workflows/profiles/quick-test.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 流程会生成自包含预览 `svg_final/`,并把 `svg_output/` 镜像到 `backup/<timestamp>/svg_output/`;PowerPoint 手工“转换为形状”不在支持范围。对事实充分、内容自包含的材料,用户可显式启用[快速生成模式](./skills/ppt-master/workflows/profiles/quick-generate.md):AI 在当前上下文直接决定页结构,跳过策略师和确认,按规范手写 SVG 后导出一个 PPTX,不生成预览、讲稿、验证报告或备份。图表和表格默认导出为 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.mdindex 5bd015b4..632dda1b 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 normal delivery 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. 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.-`finalize_svg.py` remains a mandatory Step 7 operation in the normal delivery 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-test 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 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.## Q: How does multiline text export? Can PowerPoint reflow it?@@ -201,18 +201,20 @@ A typical 10–15 page presentation takes about **10–20 minutes** with a fastIf generation feels slow, check your model's token throughput. The bottleneck is usually the model's output speed, not the scripts.-## Q: Can I use a fast mode for a few disposable test slides?+## Q: Can I generate directly without the Strategist phase?-Yes. Explicitly say that this is a **quick test** and request a small fixed-roster of self-contained slides. The Generate route then uses the-[`quick-test` profile](../skills/ppt-master/workflows/profiles/quick-test.md):-the agent hand-authors `svg_output/` and runs the test-only direct exporter.+Yes. Explicitly request **quick generation** and provide fact-sufficient,+self-contained content. The Generate route then uses the+[`quick-generate` profile](../skills/ppt-master/workflows/profiles/quick-generate.md):+the agent decides the page structure in active context, hand-authors+`svg_output/` to the shared standards, and runs the direct exporter.-This mode produces only the SVG pages and one PPTX. It skips source conversion,-research, Strategist/confirmation, templates, asset acquisition, Live Preview,-quality-report files, notes, `svg_final/`, backup, animation, and narration. It-is not available for normal delivery, factual/source-backed decks, external-assets, templates, native charts/tables, or reusable output.+This profile produces only the SVG pages and one PPTX. It skips source+conversion, research, Strategist/confirmation, templates, asset acquisition,+Live Preview, quality-report files, notes, `svg_final/`, backup, animation, and+narration. Requests needing any skipped capability stay on the default+pipeline. Page count alone neither activates nor blocks quick generation. This+is a workflow 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/project-positioning.md b/docs/project-positioning.mdindex 3146828b..10b41930 100644--- a/docs/project-positioning.md+++ b/docs/project-positioning.md@@ -124,7 +124,7 @@ PPT Master is not intended to become:- An arbitrary SVG-to-PPTX or arbitrary OOXML conversion service.- A system that reconstructs missing historical Master / Layout intent from a finished PPTX or SVG.- An in-place upgrader that grafts inferred template structure onto existing files.-- A speed-first generator that sacrifices deck coherence, native editability, or delivery reliability.+- A product-wide speed-first default that sacrifices deck coherence, native editability, or delivery reliability.These non-goals do not forbid presentation-specific use of research, images, audio, native objects, or existing decks. They prevent supporting infrastructure from becoming an independent product with a different user promise.diff --git a/docs/roadmap.md b/docs/roadmap.mdindex 8bf18b6a..7518589b 100644--- a/docs/roadmap.md+++ b/docs/roadmap.md@@ -85,9 +85,12 @@ The narrow exception is the `data-pptx-replace-with` marker: independently plannIn the cost / speed / quality triangle this project picks **quality**. ~20 minutes for a high-quality PPTX is the current reasonable point.Will do: indirect improvements via prompt slimming / cache hit rate.-Won't do: trading quality for "throw a few pages together" speed.+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.-If speed-sensitive and quality-tolerant, a zero-setup browser SaaS tool is a better fit.+The default Generate pipeline continues to prefer quality over speed.### Standalone CLI / hosted SaaS / desktop app form factorsdiff --git a/docs/technical-design.md b/docs/technical-design.mdindex ab4904df..44ea6f04 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -36,7 +36,11 @@ The three layers have separate responsibilities and cannot substitute for one an## Generate PPTX Architecture-The diagram below covers the Generate PPTX route, including its `beautify-pptx` profile. 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.+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 this lifecycle. 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.```User Input (PDF/DOCX/XLSX/PPTX/URL/Markdown/topic text)@@ -92,13 +96,23 @@ Output:└── svg_output/ ← A successful copy can rebuild the PPTX from frozen authored SVG```+The explicit shortcut is deliberately smaller:++```text+Fact-sufficient self-contained content+ -> decide page structure and visual system in active context+ -> hand-author svg_output/ under the shared SVG standards+ -> svg_to_pptx.py --quick-generate+ -> exports/<name>_<timestamp>.pptx+```+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.### SVG as a Constrained Page-Design Language-For every workflow that authors or redesigns visual slides through SVG, `svg_output/` is the complete page-design authority, but SVG here means project-canonical SVG accepted by the project contract—not any SVG a browser can render. Every visible text, image, shape, diagram, chart/table fallback, background, and template-derived layout element that should appear on a slide must already exist in that page SVG or be explicitly referenced by it. Templates, `design_spec.md`, and `spec_lock.md` guide SVG authoring; the exporter does not use them as a second visual layer that fills in missing page content.+For every workflow that authors or redesigns visual slides through SVG, `svg_output/` is the complete page-design authority, but SVG here means project-canonical SVG accepted by the project contract—not any SVG a browser can render. Every visible text, image, shape, diagram, chart/table fallback, background, and template-derived layout element that should appear on a slide must already exist in that page SVG or be explicitly referenced by it. In the default pipeline, templates, `design_spec.md`, and `spec_lock.md` guide SVG authoring; `quick-generate` instead uses active-context decisions and explicit SVG values. The exporter never uses planning inputs as a second visual layer that fills in missing page content.-Minimal semantic markers do not weaken that closure. Free-design, brand-only, and `template_reuse_scope: style` pages use `pptx_structure.mode: flat`: every represented object stays Slide-local and no Master/Layout identity, layer, or placeholder metadata is authored. Export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock, removes stock content placeholders and unused built-in Layouts, and retains only the standard date/footer/slide-number capability hooks without promoting Slide content. Only `template_reuse_scope: mirror|layout` uses the structured route, where every new page declares its Master/Layout identity from the first SVG draft. Fixed Master/Layout visuals are direct atomic root children, while reusable content slots are top-level groups with explicit design-zone bounds and one compatible carrier; composite `object` regions use an explicit proxy fallback, and zero-slot Layouts are valid. `data-pptx-role` is reserved for the few structural page-frame objects whose package or animation behavior is not already expressed by specialized metadata. A semantic-legacy template package is not upgraded in place or accepted as a structured Step 3 input: create a new workspace through `create-template`, using a native PPTX's still-present package facts or an old SVG's visuals only as reference, then author new pages through the AI-derived application route. A flat project is intentionally unmapped, not legacy. Export never infers, repairs, or migrates Master/Layout structure or placeholders.+Minimal semantic markers do not weaken that closure. Free-design, brand-only, `quick-generate`, and `template_reuse_scope: style` pages use flat Slide-local ownership: every represented object stays on the Slide and no Master/Layout identity, layer, or placeholder metadata is authored. Default export materializes one clean project-owned Master plus one Blank Layout from the current color/typography lock; lockless `quick-generate` uses converter-default theme scaffolding. Neither promotes Slide content. Only `template_reuse_scope: mirror|layout` uses the structured route, where every new page declares its Master/Layout identity from the first SVG draft. Fixed Master/Layout visuals are direct atomic root children, while reusable content slots are top-level groups with explicit design-zone bounds and one compatible carrier; composite `object` regions use an explicit proxy fallback, and zero-slot Layouts are valid. `data-pptx-role` is reserved for the few structural page-frame objects whose package or animation behavior is not already expressed by specialized metadata. A semantic-legacy template package is not upgraded in place or accepted as a structured Step 3 input: create a new workspace through `create-template`, using a native PPTX's still-present package facts or an old SVG's visuals only as reference, then author new pages through the AI-derived application route. A flat project is intentionally unmapped, not legacy. Export never infers, repairs, or migrates Master/Layout structure or placeholders.| Domain | Authority ||---|---|@@ -110,7 +124,7 @@ Minimal semantic markers do not weaken that closure. Free-design, brand-only, anThis is a page-design closure rule, not a claim that SVG describes the entire PPTX package. Rebuilding the visible slide from its completed SVG is the relevant invariant; reconstructing notes, audio, timing, relationships, or direct native edits from SVG alone is not.-`svg_final/` does not change that boundary. Step 7 derives visual previews from `svg_output/`: supported bitmap/SVG resources are inlined when processing succeeds, while EMF/WMF stay external for native passthrough; unresolved ordinary images retain their original references, and the current finalizer counts those processing errors without failing the whole run. These files support IDE/browser inspection and manual insertion as SVG pictures. They are not a second PPTX export route and carry no PowerPoint Convert-to-Shape compatibility contract. Editable shapes come only from the project converter translating `svg_output/` into native DrawingML PPTX.+`svg_final/` does not change that boundary. In the default pipeline, Step 7 derives visual previews from `svg_output/`: supported bitmap/SVG resources are inlined when processing succeeds, while EMF/WMF stay external for native passthrough; unresolved ordinary images retain their original references, and the current finalizer counts those processing errors without failing the whole run. These files support IDE/browser inspection and manual insertion as SVG pictures. They are not a second PPTX export route and carry no PowerPoint Convert-to-Shape compatibility contract. Editable shapes come only from the project converter translating `svg_output/` into native DrawingML PPTX.Existing-PPTX requests split by mutation model: the two native workflows bypass SVG, while `beautify-pptx` remains a Generate PPTX profile that regenerates the visible design:@@ -132,6 +146,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 from fact-sufficient self-contained text | Generate PPTX + `quick-generate` profile | decide page structure in active context, skip Strategist/confirmation/spec/lock, hand-author SVG, and export one PPTX directly || 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 |@@ -149,7 +164,7 @@ Ambiguous "optimize this PPT" requests reduce to one discriminator: preserve the**The pipeline: AI generates SVG → post-processing converts to DrawingML (PPTX).**-The full flow breaks into three stages:+The default full flow breaks into three stages:**Stage 1 — Content Understanding & Design Planning**Source documents (PDF/DOCX/XLSX/PPTX/URL/Markdown/topic text) are converted into the content and analysis facts the Strategist needs. The Strategist confirms an open communication contract, derives a complete deck solution from it, resolves production mechanics, and produces the design specification.@@ -160,6 +175,10 @@ The Executor role generates each slide as an SVG file. The output of this stage**Stage 3 — Engineering Conversion**Post-processing scripts convert supported SVG vector elements to DrawingML. Text and vector shapes stay native PowerPoint objects — clickable, editable, and restylable — while raster assets are copied as PPT picture media instead of flattening the slide into one image.+`quick-generate` skips Stage 1 and the default report-producing gates. It still+authors under the shared SVG standards and uses the same DrawingML converter,+which performs in-memory ZIP and published-Slide-count validation.+---## Artifact Flow@@ -184,6 +203,11 @@ design_spec.md + spec_lock.md + images/ + icons/ + templates/└─> svg_to_pptx.py -> exports/<name>_<ts>.pptx + validation/<output_stem>.report.jsonbackup/<ts>/svg_output/ [default output path; copy is best-effort after directory creation]+Quick Generate:+conversation or directly readable text/Markdown+ └─> active-context page/design decisions -> svg_output/+ └─> svg_to_pptx.py --quick-generate -> exports/*.pptx+Direct OOXML routes:analysis/<stem>.slide_library.json + source PPTX + fill_plan.json└─> template_fill_pptx.py -> exports/*.pptx@@ -253,7 +277,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 test-only [`quick-test`](../skills/ppt-master/workflows/profiles/quick-test.md) profile bypasses that lifecycle and creates only `svg_output/` plus the PPTX destination. The normal delivery lifecycle is:+`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 bypasses that lifecycle and creates only `svg_output/` plus the PPTX destination. The default delivery lifecycle is:| Directory | Role ||---|---|@@ -284,11 +308,11 @@ These invariants are stronger than ordinary implementation preferences. If a cha|---|---|| `sources/` content-type files are the main-pipeline content contract | text, tables, and chart values come from content-type files in `sources/` (Markdown is primary, but `.txt` / `.csv` / `.json` / `.yaml` / … count too); known sidecars (`*.conversion_profile.json`, `*_files/image_manifest.json`) are excluded || `analysis/` stores machine facts, not design contracts | `source_profile.json` and intake artifacts inform Strategist; they do not lock page count/order except in workflows that say so |-| `design_spec.md` explains the design; `spec_lock.md` executes it | both remain owning artifacts; an on-demand projection never replaces them |+| `design_spec.md` explains the design; `spec_lock.md` executes it in the default pipeline | both remain owning artifacts there; `quick-generate` persists neither and keeps its minimal choices in active context || Planning context is retained until invalidated | continuous execution reuses the complete Design Spec, lock, and triggered references; fresh/resumed/restarted or compacted execution reloads them once || `page-context` is on demand | the read-only projector supports diagnostics, deterministic routing checks, and optional usage telemetry; it is not a pre-page gate || `svg_output/` is the only hand-authored SVG directory | quality checks, manual edits, re-export, and `update_spec.py` target authored source |-| `svg_final/` is mandatory but derived in normal delivery | it is regenerated from `svg_output/` for visual preview or manual insertion as an SVG picture; supported resources are inlined when possible while EMF/WMF retain an external-reference exception, and it never becomes the native export source of truth; quick-test skips this artifact |+| `svg_final/` is mandatory but derived in default delivery | it is regenerated from `svg_output/` for visual preview or manual insertion as an SVG picture; supported resources are inlined when possible while EMF/WMF retain an external-reference exception, and it never becomes the native export source of truth; quick-generate skips this artifact || Native PPTX export reads `svg_output/` by default | converter preserves icons, `preserveAspectRatio`, rounded rects, and native image crop metadata before finalization rewrites them || PowerPoint Convert to Shape is outside the compatibility contract | `svg_final/` may be inserted as an SVG picture, but the converted structure and visual result are not guaranteed and do not constrain the supported SVG feature set || Direct OOXML routes do not enter the SVG pipeline | preservation workflows patch native PPTX parts directly |@@ -374,19 +398,19 @@ in the Design Spec, but it never rewrites the raw speaker-notes choice.## Execution Discipline-Generate execution is governed by [`workflows/generate-pptx.md`](../skills/ppt-master/workflows/generate-pptx.md), which owns Step 1–7 and the generation-specific rules; [`SKILL.md`](../skills/ppt-master/SKILL.md) owns only global execution discipline and the mandatory handoff to `routing.md`. Together, these rules may look bureaucratic but exist because LLMs default to "let me solve the whole problem in this turn", which is exactly the wrong shape for a serial pipeline where each step's output is bounded, checkpointed, and consumed by the next. They close failure modes that surfaced repeatedly in practice: out-of-order execution, AI proxying user design decisions, cross-phase bundling, missing prerequisites, speculative pre-work, sub-agent context loss, page-batching drift, long-deck color/font drift, batch/script-generated SVG drift, and routing ambiguity.+Generate execution is governed by [`workflows/generate-pptx.md`](../skills/ppt-master/workflows/generate-pptx.md), which owns the default Step 1–7 sequence, the explicit quick-generation short circuit, and the generation-specific rules; [`SKILL.md`](../skills/ppt-master/SKILL.md) owns only global execution discipline and the mandatory handoff to `routing.md`. Together, these rules may look bureaucratic but exist because LLMs default to "let me solve the whole problem in this turn", which is exactly the wrong shape for a serial pipeline where each step's output is bounded, checkpointed, and consumed by the next. They close failure modes that surfaced repeatedly in practice: out-of-order execution, AI proxying user design decisions, cross-phase bundling, missing prerequisites, speculative pre-work, sub-agent context loss, page-batching drift, long-deck color/font drift, batch/script-generated SVG drift, and routing ambiguity.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, Executor 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, generation cadence is fixed as `P01 → first-page gate → uninterrupted remaining pages → final gate`. P01 is a method sample, not merely a visual mock: execution emits a `gate-signal` separating method-level, page-local, and not-yet-exercised capabilities, then carries resolved method rules into later pages. No checker call or page batch interrupts P02 through the final page. 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 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.-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.+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.---## Spec Propagation: spec_lock.md as Contextual Execution Contract-The Strategist phase produces two artifacts that look redundant but serve different masters:+In the default pipeline, the Strategist phase produces two artifacts that look redundant but serve different masters:- `design_spec.md` — human-readable narrative; the "why" of the deck (communication intent, audience outcome, narrative / template / visual rationale, page outline)- `spec_lock.md` — machine-readable execution contract; the compact `audience` / `objective` / `core_message` communication anchors plus stable identity/reuse roles and routing values (core HEX/font roles, icon library, image resources, and structure mappings)@@ -409,7 +433,9 @@ The tool refuses to back up: it relies on git for revert. Adding a backup mechan## Materials → Plan → Realization: the Kitchen Contract-The cooking analogy is the canonical ownership model for generation, not just explanatory prose:+The cooking analogy is the canonical ownership model for the default Generate+pipeline, not just explanatory prose. `quick-generate` deliberately omits its+planning and preparation layers under the narrower profile contract.| Restaurant | PPT Master | Authority ||---|---|---|@@ -491,7 +517,7 @@ The architectural reasons worth knowing here:**Why placed before post-processing, not after.** Post-processing rewrites SVG (icon embedding, image inlining), which would mask source-level violations. Reading `svg_output/` directly catches the Executor's actual output, before any cleanup that might paper over a bug.-**Why there are first-page and final checks.** The P01 gate treats the first page as a method sample: it separates method-level, page-local, and not-yet-exercised capabilities, reviews the complete issue set, then fixes every blocking error and selected advisory warnings in one consolidated loop. After it passes, P02 through the final page are generated continuously without checker calls; only the final gate inspects the complete authored set before release. The first calibrates method, while the second verifies the whole deck, so neither substitutes for the other.+**Why the default pipeline has first-page and final checks.** The P01 gate treats the first page as a method sample: it separates method-level, page-local, and not-yet-exercised capabilities, reviews the complete issue set, then fixes every blocking error and selected advisory warnings in one consolidated loop. After it passes, P02 through the final page are generated continuously without checker calls; only the final gate inspects the complete authored set before release. The first calibrates method, while the second verifies the whole deck, so neither substitutes for the other.**Severity model: errors block, warnings do not, and there is intentionally no auto-fix.** Severity is determined by whether the input maps deterministically and legally, not merely by whether it uses the recommended spelling:@@ -536,7 +562,7 @@ Validation JSON files are cold audit artifacts, not routine model inputs. The exThis is easy to miss when reading the code. Shared cleanup modules, the local-reference expander, and the inline-geometry materializer are used both to write `svg_final/` and in memory during native conversion. The checker, editor, and structure parser also share parts of the geometry interpretation, but they are not artifact consumers in this section.-**Disk consumer** — in normal delivery, `finalize_svg.py` writes `svg_output/` → `svg_final/` once per run, expanding both project icon placeholders and qualified local `<use>` references. This mandatory normal-flow output feeds IDE/browser preview and may be inserted manually as an SVG picture; it is not converted into a separate PPTX artifact. Quick-test skips the disk consumer.+**Disk consumer** — in the default Generate flow, `finalize_svg.py` writes `svg_output/` → `svg_final/` once per run, expanding both project icon placeholders and qualified local `<use>` references. This mandatory default-flow output feeds IDE/browser preview and may be inserted manually as an SVG picture; it is not converted into a separate PPTX artifact. Quick-generate skips the disk consumer.**Memory consumer** — native pptx generation reads `svg_output/` directly (no disk hop). It materializes author SVG inline geometry, expands project icon placeholders, materializes geometry injected by those icons, expands qualified local `<use>` references, and finally processes positional text runs:@@ -673,7 +699,7 @@ Supporting files stay separate only to keep route contracts focused and load opt| Class | Runbooks | Owning route ||---|---|---|-| Generation profile | `beautify-pptx` | Generate PPTX with wording, page count, and page order frozen 1:1 |+| Generation profiles | `beautify-pptx`, `quick-generate` | Generate PPTX with either wording/page invariants or the explicit direct SVG-to-PPTX short circuit || Template child workflows | `create-brand`, `create-layout`, `create-deck` | Create Template dispatches exactly one for identity-only, brand-neutral/application-neutral structure, or a recurring application with integrated identity/structure || Template-input stage | `apply-template-workspace` | Generate PPTX Step 3; loaded only when an explicit workspace-root path triggers it || Generation stages | `topic-research`, `resume-execute`, `refine-spec`, `verify-charts`, `visual-review`, `live-preview`, `customize-animations` | Generate PPTX at their defined intake, planning, editing, quality, or post-processing points |diff --git a/docs/zh/faq.md b/docs/zh/faq.mdindex 3b277069..18fcf152 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/`。在正式交付流程中,Executor 的原始 SVG 源(`svg_output/` 副本)会镜像到 `backup/<timestamp>/svg_output/`,便于归档或基于该版重跑 `finalize_svg → svg_to_pptx` 重建 PPTX,无需再走 LLM。+可以。SVG 管线统一由项目转换器读取 `svg_output/` 并生成原生 DrawingML `.pptx`;文字、图形和颜色无需额外转换即可编辑,文件以时间戳命名保存至 `exports/`。在默认 Generate 流程中,Executor 的原始 SVG 源(`svg_output/` 副本)会镜像到 `backup/<timestamp>/svg_output/`,便于归档或基于该版重跑 `finalize_svg → svg_to_pptx` 重建 PPTX,无需再走 LLM。-正式交付的 Step 7 仍会强制生成 `svg_final/`。其中每页都是自包含的视觉预览 SVG,可直接在浏览器或 IDE 中打开,也可作为 SVG 图片手动插入 PowerPoint;显式快速测试会跳过预览和备份产物。项目只保证 `svg_final/` 作为预览或图片显示,不保证 PowerPoint 手工“转换为形状”后的结果。需要可编辑形状时,请使用 `exports/` 中由项目转换器生成的原生 PPTX。+默认 Generate 流程的 Step 7 仍会强制生成 `svg_final/`。其中每页都是自包含的视觉预览 SVG,可直接在浏览器或 IDE 中打开,也可作为 SVG 图片手动插入 PowerPoint;显式快速生成会跳过预览和备份产物。项目只保证 `svg_final/` 作为预览或图片显示,不保证 PowerPoint 手工“转换为形状”后的结果。需要可编辑形状时,请使用 `exports/` 中由项目转换器生成的原生 PPTX。## Q: 多行文本会怎样导出?可以让 PowerPoint 自动重排吗?@@ -202,11 +202,11 @@ python3 skills/ppt-master/scripts/svg_to_pptx.py <project> -a auto --animation-t如果感觉生成很慢,检查一下模型的 token 吞吐速度。瓶颈通常在模型的输出速度,而不是脚本本身。-## Q: 临时测试几页 PPT,可以走快速模式吗?+## Q: 可以跳过策略师阶段直接生成吗?-可以。请明确说明这是一次**快速测试**,并给出少量、固定、自包含的页面清单。Generate 路线会启用 [`quick-test` profile](../../skills/ppt-master/workflows/profiles/quick-test.md):AI 直接手写 `svg_output/`,随后调用测试专用的直接导出器。+可以。请显式要求**快速生成**,并提供事实充分、内容自包含的材料。Generate 路线会启用 [`quick-generate` profile](../../skills/ppt-master/workflows/profiles/quick-generate.md):AI 在当前上下文直接决定页结构,按共享规范手写 `svg_output/`,随后调用直接导出器。-该模式只产出 SVG 页面和一个 PPTX;不会做源文件转换、事实研究、策略师规划与确认、模板套用、素材获取、Live Preview、质量报告、讲稿、`svg_final/`、备份、动画或旁白。正式交付、需要事实或源文件、依赖外部素材/模板/原生图表表格,或要求复用时,仍走标准流程。+该 profile 只产出 SVG 页面和一个 PPTX;不会做源文件转换、事实研究、策略师规划与确认、模板套用、素材获取、Live Preview、质量报告、讲稿、`svg_final/`、备份、动画或旁白。需要任一被跳过能力时仍走默认流程;页数本身既不会自动触发,也不会阻止快速生成。这是工作流短路,不承诺具体耗时,也不承诺与默认流程质量等价。## Q: 长 PPT 一次生成会不会上下文爆掉?diff --git a/docs/zh/project-positioning.md b/docs/zh/project-positioning.mdindex a62b1df2..8bfe9427 100644--- a/docs/zh/project-positioning.md+++ b/docs/zh/project-positioning.md@@ -124,7 +124,7 @@ PPT Master 不以成为以下产品为目标:- 任意 SVG 到 PPTX 或任意 OOXML 的转换服务。- 从完成态 PPTX 或 SVG 中恢复缺失的历史 Master / Layout 意图。- 把推断出的模板结构原地嫁接到已有文件上的升级器。-- 以牺牲 deck 一致性、原生可编辑性或交付可靠性为代价的速度优先生成器。+- 以牺牲 deck 一致性、原生可编辑性或交付可靠性为代价的产品级默认速度优先生成器。这些非目标并不排斥在演示任务中使用研究、图片、音频、原生对象或已有 deck。它们防止支撑能力脱离演示语境,发展成承诺完全不同的独立产品。diff --git a/docs/zh/roadmap.md b/docs/zh/roadmap.mdindex 0c576e23..61000b2a 100644--- a/docs/zh/roadmap.md+++ b/docs/zh/roadmap.md@@ -84,10 +84,11 @@ Generate PPTX 路线围绕完全可控的新形状、文字与版式创作。结成本 / 速度 / 质量三角下,本项目选择**质量优先**。20 分钟生成一个高质量 PPTX 是当前的合理点。-会做:通过 prompt 精简 / 缓存命中率提升带来的间接改善;-不会做:以牺牲质量为代价的「随便几页应付交差」式提速。+会做:通过 prompt 精简 / 缓存命中率提升带来的间接改善。-如果对速度敏感且能接受质量下降,零配置的浏览器 SaaS 工具更合适。+显式 `quick-generate` 是用户主动选择的工作流短路,不是默认流程的保质提速:它跳过 Strategist、确认和生成报告的质量门,随后直接创作 SVG 并导出。它不承诺具体耗时,也不承诺与默认流程质量等价。++默认 Generate 流程仍坚持质量优先。### 独立 CLI / 托管 SaaS / 桌面 App 形态diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 0674c3ae..9f053d35 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。Create Template 有独立的工作区生命周期;Fill Native PPTX 与 Enhance Native PPTX 直接操作 OOXML。本文后续路线表会覆盖全部四条顶层路线。+下图描述 Generate PPTX 的默认生命周期,也包含其 `beautify-pptx` profile。显式 `quick-generate` profile 仍属于同一路线,但会绕过这套生命周期。Create Template 有独立的工作区生命周期;Fill Native PPTX 与 Enhance Native PPTX 直接操作 OOXML。本文后续路线表会覆盖全部四条顶层路线。```用户输入 (PDF/DOCX/XLSX/PPTX/URL/Markdown/主题文本)@@ -92,13 +92,23 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使└── svg_output/ ← 成功复制时可由冻结作者源重建 pptx```+显式短路流程更小:++```text+事实充分、内容自包含的材料+ -> 在当前上下文决定页结构与视觉系统+ -> 按共享 SVG 规范手写 svg_output/+ -> svg_to_pptx.py --quick-generate+ -> exports/<name>_<timestamp>.pptx+```+未显式指定 `-o` 时,native 与 narration 标记可以组合成 `<project_name>_<timestamp>_native_charts_tables_narrated.pptx`;显式 `-o` 则保留调用者给定的文件名。### SVG 是受约束的页面设计语言-凡是通过 SVG 创作或重新设计页面的工作流,`svg_output/` 都是完整的页面设计权威,但这里的 SVG 专指通过项目合同校验的项目规范化 SVG,而不是任意浏览器可渲染的 SVG。最终幻灯片中应出现的文字、图片、形状、图示、图表 / 表格 fallback、背景和模板派生布局元素,都必须已经存在于对应页面 SVG 中,或被它明确引用。模板、`design_spec.md` 和 `spec_lock.md` 负责指导 SVG 创作;导出器不能把它们当成第二层画面来源,在导出阶段补入 SVG 缺失的页面内容。+凡是通过 SVG 创作或重新设计页面的工作流,`svg_output/` 都是完整的页面设计权威,但这里的 SVG 专指项目合同接受的项目规范化 SVG,而不是任意浏览器可渲染的 SVG。最终幻灯片中应出现的文字、图片、形状、图示、图表 / 表格 fallback、背景和模板派生布局元素,都必须已经存在于对应页面 SVG 中,或被它明确引用。默认流程由模板、`design_spec.md` 和 `spec_lock.md` 指导 SVG 创作;`quick-generate` 则使用当前上下文决策和 SVG 中的显式值。导出器不能把规划输入当成第二层画面来源,在导出阶段补入 SVG 缺失的页面内容。-最小语义标记不会削弱这条闭包。自由设计、brand-only 和 `template_reuse_scope: style` 页面使用 `pptx_structure.mode: flat`:所有已表达对象保持 Slide 本地,不创作任何 Master/Layout 身份、分层或 placeholder metadata。导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout,删除 title/body 等内置内容占位符与未使用的内置 Layout,仅保留标准日期、页脚和页码能力钩子,但不提升任何 Slide 内容。只有 `template_reuse_scope: mirror|layout` 使用 structured 路线,每张新页面从第一版 SVG 起就声明 Master/Layout 身份。固定 Master/Layout 视觉是根节点直接原子元素;可复用内容槽位是顶层 group,带显式设计区域 bounds 和一个兼容 carrier;复合 `object` 区域走显式 proxy 降级,Layout 也允许零槽。`data-pptx-role` 只补充专用 metadata 尚未表达的少量页面框架、package 或动画行为。带旧结构语义的模板包不能原地升级,也不能作为 Step 3 的 structured 输入:先通过 `create-template` 创建新工作区;原生 PPTX 只提供包内仍然存在的事实,旧 SVG 只作为视觉参考;随后由 Generate PPTX 路线按照 AI 推导的应用计划创作新页面。flat 项目是有意不带 mapping,不算 legacy。导出器不推断、修补或迁移 Master/Layout 结构与 placeholder。+最小语义标记不会削弱这条闭包。自由设计、brand-only、`quick-generate` 和 `template_reuse_scope: style` 页面都采用 flat 的 Slide 本地所有权:所有已表达对象保持在 Slide,不创作 Master/Layout 身份、分层或 placeholder metadata。默认导出器根据当前配色/字体 lock 生成一个属于本项目的干净 Master 和一个 Blank Layout;无 lock 的 `quick-generate` 使用转换器默认 theme 壳。两者都不会提升任何 Slide 内容。只有 `template_reuse_scope: mirror|layout` 使用 structured 路线,每张新页面从第一版 SVG 起就声明 Master/Layout 身份。固定 Master/Layout 视觉是根节点直接原子元素;可复用内容槽位是顶层 group,带显式设计区域 bounds 和一个兼容 carrier;复合 `object` 区域走显式 proxy 降级,Layout 也允许零槽。`data-pptx-role` 只补充专用 metadata 尚未表达的少量页面框架、package 或动画行为。带旧结构语义的模板包不能原地升级,也不能作为 Step 3 的 structured 输入:先通过 `create-template` 创建新工作区;原生 PPTX 只提供包内仍然存在的事实,旧 SVG 只作为视觉参考;随后由 Generate PPTX 路线按照 AI 推导的应用计划创作新页面。flat 项目是有意不带 mapping,不算 legacy。导出器不推断、修补或迁移 Master/Layout 结构与 placeholder。| 领域 | 权威来源 ||---|---|@@ -110,7 +120,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使这是一条“页面设计闭包”规则,不代表 SVG 要描述完整 PPTX package。相关验收是:完成的页面 SVG 能重建对应幻灯片的可见设计;不要求仅凭 SVG 重建讲稿、音频、计时、relationships 或直接原生编辑结果。-`svg_final/` 不改变这条边界。Step 7 必须从 `svg_output/` 派生视觉预览:受支持的位图 / SVG 资源会内联,EMF/WMF 为 native passthrough 保留外部引用;无法解析的普通图片会保留原引用,当前 finalizer 只统计这类处理错误,并不据此让整次处理失败。这组文件供 IDE、浏览器查看,也可由用户手动作为 SVG 图片插入 PowerPoint;它不是第二条 PPTX 导出路线,也不承担 PowerPoint 手工“转换为形状”的兼容性。需要可编辑形状时,唯一受支持的路径是项目转换器把 `svg_output/` 翻译为原生 DrawingML PPTX。+`svg_final/` 不改变这条边界。默认流程的 Step 7 必须从 `svg_output/` 派生视觉预览:受支持的位图 / SVG 资源会内联,EMF/WMF 为 native passthrough 保留外部引用;无法解析的普通图片会保留原引用,当前 finalizer 只统计这类处理错误,并不据此让整次处理失败。这组文件供 IDE、浏览器查看,也可由用户手动作为 SVG 图片插入 PowerPoint;它不是第二条 PPTX 导出路线,也不承担 PowerPoint 手工“转换为形状”的兼容性。需要可编辑形状时,唯一受支持的路径是项目转换器把 `svg_output/` 翻译为原生 DrawingML PPTX。已有 PPTX 请求按修改模型分流:两条原生工作流绕过 SVG,`beautify-pptx` 则仍是 Generate PPTX 内部通过 SVG 重做可见设计的 profile:@@ -132,6 +142,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使|---|---|---|| 只有主题,或现有材料缺少实现用户目标所需的事实 | Generate PPTX Step 1 内运行 `topic-research` | 只有主题时立即研究;有材料时先转换 / 阅读,只补已识别的事实缺口 || 有源文件或对话文本,deck 结构可以重想 | Generate PPTX | Strategist 可以拆分、合并、删除、重排和重设计 |+| 对事实充分、自包含的文本显式要求快速生成 | Generate PPTX + `quick-generate` profile | 在当前上下文决定页结构,跳过 Strategist / 确认 / spec / lock,手写 SVG 后直接导出一个 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 重新生成;内容和分页锁定 |@@ -149,7 +160,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使**核心流程:AI 生成 SVG → 后处理转换为 DrawingML(PPTX)。**-整个流程分为三个阶段:+默认完整流程分为三个阶段:**第一阶段:内容理解与设计规划**源文档(PDF/DOCX/XLSX/PPTX/URL/Markdown/主题文本)会被转换成 Strategist 所需的内容事实与分析事实。Strategist 先确认开放式沟通契约,再由此推导完整 PPT 方案、解决生产机制,最终输出完整设计规格。@@ -160,6 +171,8 @@ Executor 角色逐页生成演示文稿的视觉内容,输出为 SVG 文件。**第三阶段:工程化转换**后处理脚本将受支持的 SVG 向量元素转换为 DrawingML。文本和向量形状会保持为 PowerPoint 原生对象——可点击、可编辑、可改样式;位图资源则复制为 PPT picture media,而不是把整页压平成一张图片。+`quick-generate` 跳过第一阶段及默认流程中生成报告的门禁,但仍按共享 SVG 规范创作,并使用同一个 DrawingML 转换器;转换器继续在内存中校验 ZIP 完整性和已发布 Slide 数量。+---## 产物流@@ -184,6 +197,11 @@ design_spec.md + spec_lock.md + images/ + icons/ + templates/└─> svg_to_pptx.py -> exports/<name>_<ts>.pptx + validation/<output_stem>.report.jsonbackup/<ts>/svg_output/ [默认输出路径;目录创建后复制为 best-effort]+Quick Generate:+对话或可直接读取的文本 / Markdown+ └─> 当前上下文中的页结构与设计决策 -> svg_output/+ └─> svg_to_pptx.py --quick-generate -> exports/*.pptx+直接 OOXML 路由:analysis/<stem>.slide_library.json + 源 PPTX + fill_plan.json└─> template_fill_pptx.py -> exports/*.pptx@@ -253,7 +271,7 @@ SVG 也是唯一同时满足流程中所有角色需要的格式:**AI 能可## 项目结构与生命周期-`project_manager.py init` 创建固定的项目工作目录;默认导出随后创建带时间戳的备份目录,再尝试复制 `backup/` 快照。完整生命周期结构如下:+`project_manager.py init` 创建固定的项目工作目录;默认导出随后创建带时间戳的备份目录,再尝试复制 `backup/` 快照。显式 [`quick-generate`](../../skills/ppt-master/workflows/profiles/quick-generate.md) profile 绕过该生命周期,只创建 `svg_output/` 和 PPTX 目标。默认交付生命周期如下:| 目录 | 职责 ||---|---|@@ -284,11 +302,11 @@ CLI 支持 `--move`、`--copy` 和自动默认,但共享同一条固定的所|---|---|| `sources/` 内容型文件是主流水线内容契约 | 主 SVG 路线中的文本、表格和图表数值来自 `sources/` 内容型文件(Markdown 为主,`.txt` / `.csv` / `.json` / `.yaml` 等同样计入);已知 sidecar(`*.conversion_profile.json`、`*_files/image_manifest.json`)排除在外 || `analysis/` 存机器事实,不存设计契约 | `source_profile.json` 和 intake artifact 辅助 Strategist;除非工作流明确规定,否则不锁定页数 / 页序 |-| `design_spec.md` 解释设计;`spec_lock.md` 执行设计 | 两者始终是权威产物;按需投影不会取代它们 |+| 默认流程由 `design_spec.md` 解释设计、`spec_lock.md` 执行设计 | 两者在默认流程中始终是权威产物;`quick-generate` 不落盘二者,只在当前上下文保留最小设计选择 || 规划上下文有效时持续复用 | 连续执行直接使用完整 Design Spec、lock 与已触发引用;fresh/resumed/restarted 或压缩后才重新读取一次 || `page-context` 按需调用 | 只读投影器用于诊断、确定性路由检查和可选的用量统计,不是逐页门禁 || `svg_output/` 是唯一手写 SVG 目录 | 质量检查、手工编辑、重导出和 `update_spec.py` 都面向作者源 |-| `svg_final/` 是派生产物 | 它必须能从 `svg_output/` 重建,只负责视觉预览;受支持资源尽量内联,EMF/WMF 保留外链例外,不应成为 native 导出的事实源 |+| `svg_final/` 是默认流程派生产物 | 它必须能从 `svg_output/` 重建,只负责视觉预览;受支持资源尽量内联,EMF/WMF 保留外链例外,不应成为 native 导出的事实源;`quick-generate` 跳过它 || native PPTX 标准导出读取 `svg_output/` | 唯一受支持的可编辑形状路线由项目转换器执行;它要在 finalize 重写前保留图标、`preserveAspectRatio`、圆角矩形和原生图片裁剪语义 || PowerPoint 手工“转换为形状”不属于兼容性契约 | `svg_final/` 可以作为 SVG 图片插入,但转换后的结构与视觉结果不做保证,也不反向约束 SVG 允许能力 || 直接 OOXML 路由不进入 SVG 流水线 | 保留型工作流直接 patch 原生 PPTX parts |@@ -368,19 +386,19 @@ Stage 3 的三个主动执行值始终保留为相互独立的原始证据。尤## 执行纪律-Generate 执行以 [`workflows/generate-pptx.md`](../../skills/ppt-master/workflows/generate-pptx.md) 为权威,该文档拥有 Step 1–7 与 Generate 专属规则;[`SKILL.md`](../../skills/ppt-master/SKILL.md) 只拥有全局执行纪律,以及交接到 `routing.md` 的强制入口。这些规则整体看起来很官僚,但存在的理由是:LLM 默认行为是“让我在这一 turn 里把整个问题搞定”,而这恰好是串行流水线最不该有的形状——串行流水线要求每一步的输出都是有界、过 checkpoint、被下一步消费的。它们共同关闭了实际反复出现的失败模式:乱序执行、AI 代为做用户设计决策、跨阶段打包、前置条件未满足、投机预先准备、子代理上下文丢失、分批漂移、长 deck 色彩字体漂移、脚本批量生成 SVG 漂移,以及路由歧义。+Generate 执行以 [`workflows/generate-pptx.md`](../../skills/ppt-master/workflows/generate-pptx.md) 为权威,该文档拥有默认 Step 1–7、显式快速生成短路与 Generate 专属规则;[`SKILL.md`](../../skills/ppt-master/SKILL.md) 只拥有全局执行纪律,以及交接到 `routing.md` 的强制入口。这些规则整体看起来很官僚,但存在的理由是:LLM 默认行为是“让我在这一 turn 里把整个问题搞定”,而这恰好是串行流水线最不该有的形状——串行流水线要求每一步的输出都是有界、过 checkpoint、被下一步消费的。它们共同关闭了实际反复出现的失败模式:乱序执行、AI 代为做用户设计决策、跨阶段打包、前置条件未满足、投机预先准备、子代理上下文丢失、分批漂移、长 deck 色彩字体漂移、脚本批量生成 SVG 漂移,以及路由歧义。全路由通用的停止 / 继续规则以 [`failure-recovery.md`](../../skills/ppt-master/workflows/governance/failure-recovery.md) 为准;其中具体故障矩阵与续跑入口目前覆盖 Generate PPTX。本节不复制这些规则。-其中三条边界尤其关键。第一,Executor 页面 SVG 必须由当前主代理逐页手写;禁止写 Python / Node / shell 生成器批量吐 SVG,因为这种输出会丢失跨页判断和视觉连续性。第二,生成节奏固定为 `P01 → first-page gate → 不间断生成其余页面 → final gate`。P01 不只是单页样张:执行者必须先输出 `gate-signal`,区分 method-level、page-local 与未覆盖的能力,再把已解决的方法规则带入后续页面;P02 到末页之间不分批,也不插入 checker 调用。第三,路由是确定性的:原生 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 为视觉锚点,但跳过两道 checker gate。第三,路由是确定性的:原生 PPTX 模板、beautify、native enhancement、自定义动画、live preview 等触发条件已经在仓库里定义清楚时,不再额外抛给用户一个开放式路线选择题。-角色切换协议(切换模式前必须 `read_file references/<role>.md`)有两个互相支撑的作用:把新鲜的角色指令载入上下文,覆盖前一模式的漂移;对话 transcript 中的可见标记构成审计轨迹,让用户能看到 agent 何时切换了模式——回看一个具体决策为什么这样做时,这条线索很关键。+默认流程的角色切换协议(切换模式前必须 `read_file references/<role>.md`)有两个互相支撑的作用:把新鲜的角色指令载入上下文,覆盖前一模式的漂移;对话 transcript 中的可见标记构成审计轨迹,让用户能看到 agent 何时切换了模式——回看一个具体决策为什么这样做时,这条线索很关键。---## 设计规范的传播:spec_lock.md 作为上下文执行契约-Strategist 阶段产出两份看起来冗余但服务不同对象的产物:+默认流程的 Strategist 阶段产出两份看起来冗余但服务不同对象的产物:- `design_spec.md` —— 人类可读叙述;deck 的「为什么」(沟通意图、受众变化、叙事 / 模板 / 视觉理由、页面大纲)- `spec_lock.md` —— 机器可读执行契约;包含紧凑的 `audience` / `objective` / `core_message` 沟通锚点,以及跨页稳定的身份/复用角色和路由值(核心 HEX/字体角色、图标库、图片资源与结构映射)@@ -403,7 +421,7 @@ Strategist 阶段产出两份看起来冗余但服务不同对象的产物:## 材料 → 规划 → 实现:餐厅合同-“做饭”不是临时解释,而是生成流程的正式所有权模型:+“做饭”不是临时解释,而是默认 Generate 流程的正式所有权模型。`quick-generate` 按更窄的 profile 合同显式省略规划与备料层:| 餐厅角色 | PPT Master 对应项 | 决策权 ||---|---|---|@@ -485,7 +503,7 @@ SVG 与 DrawingML 的表达模型并不等价,因此主编译路径不把“**为什么放在后处理之前,而不是之后。** 后处理会重写 SVG(图标嵌入、图片内联),会掩盖源级别违规。直接读 `svg_output/` 抓的是 Executor 的实际输出,先于任何可能掩盖 bug 的清理动作。-**为什么有 first-page 与 final 两道检查。** P01 gate 把第一张页面当作方法样本:先区分 method-level、page-local 与未覆盖能力,完整审阅该轮 issue set,再在合并修复循环中消除全部 blocking error,并处理选定的 advisory warning。通过后,P02 到末页连续生成且不插入 checker;final gate 才对完整作者源做发布前检查。前者校准方法,后者验证全集,不能互相替代。+**为什么默认流程有 first-page 与 final 两道检查。** P01 gate 把第一张页面当作方法样本:先区分 method-level、page-local 与未覆盖能力,完整审阅该轮 issue set,再在合并修复循环中消除全部 blocking error,并处理选定的 advisory warning。通过后,P02 到末页连续生成且不插入 checker;final gate 才对完整作者源做发布前检查。前者校准方法,后者验证全集,不能互相替代。**严重性模型:error 阻塞、warning 不阻塞,且有意没有 auto-fix。** 严重性不按“是否符合推荐写法”划分,而按“能否确定、合法地映射”划分:@@ -530,7 +548,7 @@ SVG 与 DrawingML 的表达模型并不等价,因此主编译路径不把“这是读代码时容易忽略的关键事实。共享清理模块、本地引用展开器和 inline geometry materializer 一方面写盘生成 `svg_final/`,另一方面在 native 转换中以内存形式复用。Checker、编辑器和结构解析器也共享部分几何解释,但不属于本节的产物消费者。-**写盘消费者** —— `finalize_svg.py` 每次运行都把 `svg_output/` → `svg_final/` 写到磁盘一次,同时展开项目图标占位符和合规的本地 `<use>` 引用。`svg_final/` 随后供 IDE / 浏览器视觉预览及手工 SVG 图片插入使用。+**写盘消费者** —— 默认交付中,`finalize_svg.py` 每次运行都把 `svg_output/` → `svg_final/` 写到磁盘一次,同时展开项目图标占位符和合规的本地 `<use>` 引用。`svg_final/` 随后供 IDE / 浏览器视觉预览及手工 SVG 图片插入使用;`quick-generate` 跳过该写盘消费者。**内存消费者** —— native pptx 直接读 `svg_output/`(不经磁盘中转),依次物化作者 SVG 的 inline geometry、展开项目图标占位符、再次物化图标注入的 geometry、展开合规的本地 `<use>`,最后处理定位文本 run:@@ -659,7 +677,7 @@ ChartEx 导入被有意限制为 7 个已验证数据模型:`treemap`、`sunbu| 分类 | 文档 | 归属路线 ||---|---|---|-| 生成 profile | `beautify-pptx` | Generate PPTX;逐字措辞、页数与页序 1:1 冻结 |+| 生成 profile | `beautify-pptx`、`quick-generate` | Generate PPTX;分别负责逐字措辞 / 页数 / 页序不变量与显式 SVG→PPTX 直接短路 || 模板子工作流 | `create-brand`、`create-layout`、`create-deck` | Create Template 在“仅身份 / 品牌中立且应用中立的结构 / 应用契约与身份结构一体化”中只分派一个 || 模板输入阶段 | `apply-template-workspace` | Generate PPTX Step 3;只在显式工作区根目录触发时加载 || 生成阶段 | `topic-research`、`resume-execute`、`refine-spec`、`verify-charts`、`visual-review`、`live-preview`、`customize-animations` | Generate PPTX 中各自定义的 intake、planning、editing、quality 或 post-processing 节点 |diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.mdindex 730346cd..fa023f4b 100644--- a/skills/ppt-master/references/artifact-ownership.md+++ b/skills/ppt-master/references/artifact-ownership.md@@ -1,6 +1,7 @@# Artifact Ownership Specification-Global artifact ownership rules for PPT Master projects.+Global artifact ownership rules for PPT Master projects. A selected route or+profile may explicitly omit an artifact without transferring its facts.**Hard rule**: Read each fact from its owning artifact. Do not merge multiple channels into a second source of truth.diff --git a/skills/ppt-master/references/shared-standards-core.md b/skills/ppt-master/references/shared-standards-core.mdindex 712377f6..3d7f35bc 100644--- a/skills/ppt-master/references/shared-standards-core.md+++ b/skills/ppt-master/references/shared-standards-core.md@@ -426,8 +426,8 @@ helper cannot write a project, select layout, or generate a page.stroke, optional fill/stroke opacity, stroke width, line cap, and line join.Normal generated pages use `spec_lock.md` for stable semantic color anchors andchoose page-local paint from the retained Design Spec, style, and composition context.-The test-only [`quick-test`](../workflows/profiles/quick-test.md) profile has no-lock: keep every chosen paint value explicit in the SVG.+The lockless [`quick-generate`](../workflows/profiles/quick-generate.md) profile+keeps every chosen paint value explicit in the SVG.`create-template` authored templates take their values from the confirmed briefand template `design_spec.md`.Use ordinary SVG for gradients, patterns, filters, or other treatments outside@@ -530,7 +530,7 @@ continue without modification.## 3. Canvas Format Quick Reference-Use the already locked canvas id and exact viewBox. [`canvas-formats.md`](canvas-formats.md) owns format selection; this core owns only SVG conformance on that canvas. The test-only [`quick-test`](../workflows/profiles/quick-test.md) profile has no lock; its first SVG establishes the canvas and every remaining page must use the identical viewBox.+Use the already locked canvas id and exact viewBox. [`canvas-formats.md`](canvas-formats.md) owns format selection; this core owns only SVG conformance on that canvas. The lockless [`quick-generate`](../workflows/profiles/quick-generate.md) profile uses its first SVG to establish the canvas; every remaining page must use the identical viewBox.---@@ -553,12 +553,12 @@ Semantic markers are minimal compiler hints. Flat pages declare one root `data-p- **Canvas authority**: New authoring writes `viewBox="0 0 W H"` with positiveinteger pixels from the lock, or from the first SVG when the explicit- `quick-test` profile is active. Numerically equivalent spellings and positive+ `quick-generate` profile is active. Numerically equivalent spellings and positivefractional imported dimensions remain compatible; export quantizes once at`1 SVG px = 9,525 EMU`. Invalid/non-finite values, non-zero origin,non-positive size, or unsupported PowerPoint dimensions are errors. All pagesand Layout prototypes in one normal build share the numeric canvas and match- `spec_lock.md canvas.viewBox`; quick-test pages match the first SVG;+ `spec_lock.md canvas.viewBox`; quick-generate pages match the first SVG;standalone templates match `design_spec.md canvas_viewbox`. Optional root`width`/`height` do not override `viewBox`.Root `<svg>` transform is forbidden; nested crop and `<symbol viewBox>` keep@@ -580,7 +580,7 @@ These forms are needed only when the stated PPT behavior matters:| One editable PPT text frame with mixed formatting or multiline prose | Use one `<text>` per logical paragraph and non-positional `<tspan>` children for inline runs. Keep the first authored line as direct text; later lines use direct positioned `<tspan>` children that repeat parent `x` with positive relative `dy`; an all-`<tspan>` form may start at `dy="0"`. Default retains these breaks without PowerPoint wrapping; `--reflow-text` may join eligible lines. A font-size change, list marker, or larger accepted gap starts another paragraph. Sibling `<text>` elements are forbidden as one paragraph's line breaks; they remain valid for independent frames. || Stable object grouping or object-level animation anchor | Wrap the intended object in `<g id="...">`. Content grouping is **mandatory** per §4.3 — a top-level `<g id>` is also the animation anchor; it is not an optional convenience. || Native PowerPoint background promotion | Outside structured mode, the first eligible visual layer may be a direct full-canvas `<rect>` or one inside a simple single-child group. Its fill must have a registered native mapping (solid, linear/radial gradient, or preset pattern), and it must have no transform, filter, clip, rounding, or visible stroke. Export writes the fill as Slide `p:bg`; image elements remain pictures. Structured routes use the narrower explicit solid-background ownership contract in [`pptx-structure-interface.md`](./pptx-structure-interface.md). |-| Free-design / brand-only PowerPoint structure | Use `pptx_structure.mode: flat`. Keep every represented object Slide-local; export materializes one clean project-owned Master plus one Blank Layout from the current lock, removes stock content placeholders/Layout inventory, and retains only the standard date/footer/slide-number capability hooks. Do not author Master/Layout identities, layers, or placeholder slots. Quick-test uses the same flat object ownership but converter-default theme scaffolding because no lock exists. |+| Free-design / brand-only PowerPoint structure | Use `pptx_structure.mode: flat`. Keep every represented object Slide-local; export materializes one clean project-owned Master plus one Blank Layout from the current lock, removes stock content placeholders/Layout inventory, and retains only the standard date/footer/slide-number capability hooks. Do not author Master/Layout identities, layers, or placeholder slots. Quick-generate uses the same flat object ownership but converter-default theme scaffolding because no lock exists. || Reusable template-based PowerPoint Layout | Select one complete authoring SVG per page in `page_layouts`, declare each unique Master/Layout definition once, and assign pages through `page_pptx_layouts`. Strict preserves the prototype contract; adaptive retains its Master and uses a current or new Layout key already declared and assigned by Strategist. Construction cannot extend or mutate that mapping downstream. Non-mirror skin follows `spec_lock`. |**Hard rule — supported shape conversion**: Every PPT editability claim in this specification refers to the project converter reading `svg_output/` and emitting native DrawingML. `svg_final/` is a self-contained visual preview that may be inserted into PowerPoint as an SVG picture. PowerPoint's manual Convert-to-Shape operation is unsupported; do not narrow the authoring contract to its undocumented SVG subset.@@ -646,8 +646,8 @@ separate parent content group; never put them inside the preset group itself.The normal serial post-processing and export workflow belongs to[`generate-pptx.md`](../workflows/generate-pptx.md) Step 7. The explicit-test-only exception belongs to-[`quick-test.md`](../workflows/profiles/quick-test.md). This file defines SVG+direct-generation exception belongs to+[`quick-generate.md`](../workflows/profiles/quick-generate.md). This file defines SVGauthoring boundaries and intentionally does not mirror commands, flags, oroutput behavior.diff --git a/skills/ppt-master/scripts/docs/svg-pipeline.md b/skills/ppt-master/scripts/docs/svg-pipeline.mdindex 6c826de8..f8089b1d 100644--- a/skills/ppt-master/scripts/docs/svg-pipeline.md+++ b/skills/ppt-master/scripts/docs/svg-pipeline.md@@ -254,7 +254,7 @@ for operation, first, second, expected_error in rejections:run_tool("svg_quality_checker.py", svg_output, "--format", "ppt169")pptx = project / "boolean-smoke.pptx"-run_tool("svg_to_pptx.py", project, "--quick-test", "-o", pptx)+run_tool("svg_to_pptx.py", project, "--quick-generate", "-o", pptx)with zipfile.ZipFile(pptx) as archive:slides = [name@@ -546,33 +546,36 @@ warning and uses `flat`; no SVG regeneration is required. A missing `spec_lock.man explicit legacy/unknown mode, or a requested `structured` export without anexplicit current structured contract remains blocking.-Disposable few-page converter/layout tests may use the explicit-[`quick-test`](../../workflows/profiles/quick-test.md) profile:+Explicit direct generation from fact-sufficient self-contained content may use+the [`quick-generate`](../../workflows/profiles/quick-generate.md) profile:```bash-python3 scripts/svg_to_pptx.py <project_path> --quick-test+python3 scripts/svg_to_pptx.py <project_path> --quick-generate```-This test-only flag reads `svg_output/` directly, infers one consistent canvas,+This direct-export flag reads only `svg_output/`, infers one consistent canvas,uses flat converter-default package scaffolding, disables notes and motion, and-does not read or require `spec_lock.md`. It writes the PPTX only: no-`backup/`, conversion trace, or `validation/` report. ZIP integrity and Slide-count are checked in memory and reported through-`[QUICK-TEST] status=passed`. The flag rejects options that would add native+does not read or require `spec_lock.md`. It writes the PPTX only: no `backup/`,+conversion trace, or `validation/` report. ZIP integrity and Slide count are+checked in memory; non-quiet runs report+`[QUICK-GENERATE] status=passed`. The flag rejects options that would add nativedata objects, motion, narration, alternate SVG sources, or 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.For generated-project narration, follow the[`generate-audio`](../../workflows/stages/generate-audio.md) stage. It owns voiceselection, audio generation, and the narrated re-export workflow.Behavior:-- Default output (normal flow, no `-o`):+- Default output (default Generate flow, 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- `exports/` contains only final PPTX deliverables; machine-readable quality and postflight reports belong in `validation/`.-- Normal 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-test deliberately skips it.-- In normal 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-test writes no report.+- 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.- Postflight reruns ZIP integrity and published Slide count. Internal relationships,structured-package validation, transitions, and animations are enforced before thebuilder publishes the PPTX and are reported as `enforced-at-build`, not as repeated@@ -615,7 +618,7 @@ Behavior:overflow-hidden viewport; preview-safe shape clips target the inner image inviewBox coordinates, while legacy imported wrapper clips remain compatible.Both map to native picture crop/geometry when possible.-- Normal flow embeds speaker notes automatically unless `--no-notes` is used; quick-test always disables them+- The default Generate flow embeds speaker notes automatically unless `--no-notes` is used; quick-generate always disables them- 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 notesdiff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex 548ede99..630addd6 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": 397600+ "max_tokens": 397825},"file_budgets": {"AGENTS.md": 2400,@@ -172,18 +172,18 @@],"max_tokens": 62075},- "route.generate.quick-test": {- "description": "Explicit disposable Generate quick-test short circuit with the shared SVG authoring core.",+ "route.generate.quick-generate": {+ "description": "Explicit Generate direct-authoring short circuit with the shared SVG authoring core.","scope": "cumulative","include": ["bootstrap.routing"],"files": ["skills/ppt-master/workflows/generate-pptx.md",- "skills/ppt-master/workflows/profiles/quick-test.md",+ "skills/ppt-master/workflows/profiles/quick-generate.md","skills/ppt-master/references/shared-standards-core.md"],- "max_tokens": 31550+ "max_tokens": 31825},"route.generate.planning-image": {"description": "Generate-PPTX planning context after a non-none image source is proposed or confirmed; layout-catalog recall remains optional.",@@ -418,7 +418,7 @@"stage.generate.template.brand"],"files": [],- "max_tokens": 94750+ "max_tokens": 94775},"route.generate.deck-structured-no-image": {"description": "Deck-preset structured Generate-PPTX path without image acquisition.",diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex 8b243a9d..d8a52ca5 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -15,17 +15,17 @@ description: Generate PPTX route authority for source intake, planning, SVG auth- `preset_shape_svg.py` and `shape_boolean_svg.py` may provide only their documented stdout fragment(s) after the main agent chooses the object's role, operands, paint, and z-order; neither helper chooses layout or writes a page.- Gate checklists are internal verification, not user-facing output. On success, continue automatically and emit at most one compact status line when useful; on failure, report only the blocking items and required recovery.-### Quick Test Profile Short Circuit+### Quick Generate Profile Short Circuit-When the user explicitly requests quick/fast mode for a disposable test with a-small fixed roster of self-contained slides, load and follow-[`quick-test.md`](./profiles/quick-test.md). That profile owns the complete-test-only sequence and skips this route's Steps 1–7.+For an explicit quick/fast or direct-SVG request with fact-sufficient+self-contained content, follow+[`quick-generate.md`](./profiles/quick-generate.md). It owns the direct+SVG-to-PPTX sequence and skips this route's Steps 1–7.-**Hard rule — no implicit downgrade**: page count alone never selects quick-test. Normal delivery, source conversion, factual research, template use,-external assets, native data objects, notes, animation, narration, and reusable-output remain on the default pipeline below.+**Hard rule — no implicit downgrade or page cap**: page count neither selects+nor blocks quick generation. Conversion, research, templates, asset+acquisition, native data objects, notes, motion, narration, or visual review+requires the default pipeline below.### SVG Page-Design Boundary@@ -34,7 +34,7 @@ output remain on the default pipeline below.| Any route that authors or regenerates slide visuals through SVG | `svg_output/` is the complete page-design source: every visible text, image, shape, chart/table fallback, and layout element that should appear on the exported slide is present in that page SVG or referenced by it. || Templates, `design_spec.md`, and `spec_lock.md` | Authoring/control inputs. They guide SVG creation but MUST NOT supply visible slide content that is absent from the completed SVG during export. || Semantic SVG markers | Minimal rendering-neutral compiler hints used only after existing Layout/Layer/Placeholder/Native metadata has been considered. They never replace native SVG geometry, text, styles, grouping, or asset references. |-| `svg_final/` | Mandatory derived, self-contained SVG visual preview in the default pipeline. It may be opened directly or inserted into PowerPoint as an SVG picture, but it is not a supported PPTX source and carries no manual Convert-to-Shape compatibility contract. Quick-test skips it. |+| `svg_final/` | Mandatory derived, self-contained SVG visual preview in the default pipeline. It may be opened directly or inserted into PowerPoint as an SVG picture, but it is not a supported PPTX source and carries no manual Convert-to-Shape compatibility contract. Quick-generate skips it. || SVG-to-PPTX export | The only supported generated-PPTX route reads `svg_output/` and maps its content through the project converter to DrawingML/native objects. It compiles only the selected route's explicit structure contract: `flat` keeps represented content Slide-local, while `structured` may place explicitly scoped content in Master/Layout/Slide parts. It MUST NOT infer structure, upgrade `flat`, or invent new visible page content. || Native PPTX routes and presentation-behavior stages | Remain outside SVG page-design closure. `template-fill-pptx`, `native-enhance-pptx`, animations, transitions, speaker notes, narration, and package relationships are not required to round-trip through SVG. |diff --git a/skills/ppt-master/workflows/index.md b/skills/ppt-master/workflows/index.mdindex 5deda5c9..7413cacf 100644--- a/skills/ppt-master/workflows/index.md+++ b/skills/ppt-master/workflows/index.md@@ -20,6 +20,7 @@ Maintainer-only inventory for adding, moving, or removing workflow documents. Ru| ID | Class | Path | Parent / lifecycle slot ||---|---|---|---|| `beautify-pptx` | Generation profile | [`profiles/beautify-pptx.md`](./profiles/beautify-pptx.md) | Generate PPTX |+| `quick-generate` | Generation profile | [`profiles/quick-generate.md`](./profiles/quick-generate.md) | Generate PPTX direct SVG-to-PPTX short circuit || `apply-template-workspace` | Template-input stage | [`stages/apply-template-workspace.md`](./stages/apply-template-workspace.md) | Generate Step 3 || `create-brand` | Template child workflow | [`create-template/create-brand.md`](./create-template/create-brand.md) | Create Template || `create-layout` | Template child workflow | [`create-template/create-layout.md`](./create-template/create-layout.md) | Create Template |diff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.mdnew file mode 100644index 00000000..7696e7f0--- /dev/null+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -0,0 +1,126 @@+---+description: Generate profile for directly authoring a self-contained SVG deck and exporting one PPTX without Strategist planning or sidecar artifacts.+---++# Quick Generate Profile++> Generate-PPTX profile, not a top-level route. Use it when the user explicitly+> requests a direct SVG-to-PPTX shortcut and supplies enough content to author+> the deck without the default [`generate-pptx.md`](../generate-pptx.md)+> Steps 1–7.++**Trigger**: the user explicitly requests quick/fast generation or directs the+agent to skip planning/confirmation and proceed directly to SVG, and the request+contains enough content for direct authoring without conversion or research.+Page count alone never activates or blocks this profile.++---++## 1. Eligibility++| Condition | Required state |+|---|---|+| Intent | Explicit direct-generation shortcut |+| Content | Supplied in chat or directly readable text/Markdown, and sufficient without conversion or research |+| Visual inputs | Basic SVG geometry/text or already supplied self-contained data; no asset acquisition |+| Output | Only authored SVG pages and one native PPTX |++**Missing eligibility** → use the default Generate pipeline. Do not silently+discard requested capabilities to fit this profile.++**Hard rule — explicit scope only**: requests that require source conversion,+factual research, template application, external image/icon/font acquisition,+native charts/tables, speaker notes, animation, narration, or visual review stay+on the default pipeline. Supplied fact-sufficient content may use this profile;+the shortcut must not invent or externally enrich claims.++---++## 2. Minimal Authoring Contract++Always read+[`shared-standards-core.md`](../../references/shared-standards-core.md). Do not+load `executor-base.md`: its planned-project prerequisites do not apply to this+profile. Besides the conditional canvas lookup below, load a core conditional+module only when the requested SVG needs that registered feature; otherwise+keep the SVG surface to solid paint, basic geometry, text, and semantic groups.++Before writing P01, resolve the slide roster, canvas, visual direction, palette,+and typography in the active context. Do not persist a plan, invoke Strategist,+or wait for confirmation. Preserve the supplied facts and requested wording.++Use a new project path, or first verify that its `svg_output/` is empty. Never+reuse a directory containing pages from another run: the exporter publishes+every discovered SVG. Use one zero-padded width sized for the resolved roster,+such as `01_cover.svg` through `12_end.svg` or `001_cover.svg` through+`120_end.svg`.++Create only:++```text+<project_path>/+├── svg_output/+│ └── <ordered-page>.svg+└── exports/+ └── <project_name>_<timestamp>.pptx+```++**Hard rule — no default-pipeline artifacts**: do not run source conversion,+`project_manager.py init`, topic research, template application, Strategist,+Confirm UI, image/icon acquisition, Live Preview, SVG quality checker,+speaker-note generation, `finalize_svg.py`, chart verification, animation,+narration, or any supporting stage. Do not create `design_spec.md`,+`spec_lock.md`, `sources/`, `analysis/`, `images/`, `icons/`, `templates/`,+`confirm_ui/`, `notes/`, `svg_final/`, `validation/`, `backup/`, or metadata+sidecars.++**Canvas**: unless the user specifies another canvas, use `ppt169` with+`viewBox="0 0 1280 720"`. For another requested registered format, load+[`canvas-formats.md`](../../references/canvas-formats.md) and use its exact+viewBox. The first SVG establishes the export canvas; every remaining page must+match it exactly.++**Structure**: author flat, Slide-local SVG only. Include the complete visible+page in each SVG; set one root `data-pptx-page-role` from `cover`, `toc`,+`section`, `content`, or `ending`, and omit Master/Layout/layer/placeholder+metadata.++**Typography**: name an installed concrete font family in the SVG; do not depend+on a lock or generated font asset.++**Generation pacing**: the current main agent decides the page structure in the+active context, then 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.++---++## 3. Direct Export++Run one export command after every page in the resolved SVG roster exists:++```bash+python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-generate+```++`--quick-generate` reads only `svg_output/`, infers one consistent canvas, uses+a flat PowerPoint package with converter defaults, disables notes and motion,+skips lock/theme sidecars, and writes no backup, conversion trace, or validation+report. An explicit `-o <path>.pptx` may replace the default `exports/`+destination without changing the artifact boundary.++**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 and rerun this command; do not+create planning or validation-report artifacts.++```markdown+## ✅ Quick Generate Complete++- [x] Resolved SVG pages exist under `svg_output/`+- [x] One native PPTX exists under `exports/` or the explicit output path+- [x] No default-pipeline artifacts were created+- [ ] **Next**: Report the PPTX path+```diff --git a/skills/ppt-master/workflows/profiles/quick-test.md b/skills/ppt-master/workflows/profiles/quick-test.mddeleted file mode 100644index a14df386..00000000--- a/skills/ppt-master/workflows/profiles/quick-test.md+++ /dev/null@@ -1,105 +0,0 @@-----description: Test-only Generate profile for authoring a few SVG slides and exporting one PPTX without normal planning or sidecar artifacts.------# Quick Test Profile--> Generate-PPTX profile, not a top-level route. Use it only for disposable-> converter/layout tests; normal presentation delivery stays on-> [`generate-pptx.md`](../generate-pptx.md) Steps 1–7.--**Trigger**: the user explicitly requests quick/fast test mode, identifies the-deck as a test, and asks for a small fixed slide roster. A small page count alone-never activates this profile.-------## 1. Eligibility--| Condition | Required state |-|---|---|-| Intent | Explicit disposable test, not a presentation delivery |-| Page roster | Small, fixed, and named or directly inferable |-| Content | Supplied in chat and sufficient to draw without conversion or research |-| Visual inputs | Plain SVG geometry/text, or already supplied self-contained data; no asset acquisition |-| Output | Only authored SVG pages and one native PPTX |--**Missing eligibility** → use the normal Generate pipeline. Do not ask the user-to weaken a normal delivery request so it can enter this profile.--**Hard rule — explicit scope only**: this profile never activates for a factual-deck, a template-backed deck, source-file conversion, native charts/tables,-external images/icons/fonts, speaker notes, animation, narration, visual-review, or any reusable deliverable.-------## 2. Minimal Authoring Contract--Read only [`shared-standards-core.md`](../../references/shared-standards-core.md).-Load one of its conditional modules only when the user's exact SVG test needs-that registered feature; otherwise keep the SVG surface to solid paint, basic-geometry, text, and semantic groups.--Create only:--```text-<project_path>/-├── svg_output/-│ └── <ordered-page>.svg-└── exports/- └── <project_name>_<timestamp>.pptx-```--**Hard rule — no normal-pipeline artifacts**: do not run source conversion,-`project_manager.py init`, topic research, template application, Strategist,-Confirm UI, image/icon acquisition, Live Preview, SVG quality checker,-speaker-note generation, `finalize_svg.py`, chart verification, animation,-narration, or any supporting stage. Do not create `design_spec.md`,-`spec_lock.md`, `sources/`, `analysis/`, `images/`, `icons/`, `templates/`,-`confirm_ui/`, `notes/`, `svg_final/`, `validation/`, `backup/`, or metadata-sidecars.--**Canvas**: write `viewBox="0 0 W H"` on every page. The first SVG establishes-the test canvas; every remaining page must match it exactly.--**Structure**: author flat, Slide-local SVG only. Include the complete visible-page in each SVG; set one root `data-pptx-page-role` from `cover`, `toc`,-`section`, `content`, or `ending`, and omit Master/Layout/layer/placeholder-metadata.--**Typography**: name an installed concrete font family in the SVG; do not depend-on a lock or generated font asset.--**Generation pacing**: the current main agent hand-writes the fixed SVG roster-in order. Skip the normal first-page and final checker gates.-------## 3. Direct Export--Run one export command after every requested SVG exists:--```bash-python3 ${SKILL_DIR}/scripts/svg_to_pptx.py <project_path> --quick-test-```--`--quick-test` reads only `svg_output/`, infers one consistent canvas, uses a-flat PowerPoint package with converter defaults, disables notes and motion,-skips lock/theme sidecars, and writes no backup, conversion trace, or validation-report. An explicit `-o <path>.pptx` may replace the default `exports/`-destination without changing the artifact boundary.--**Validation**: success requires `[QUICK-TEST] status=passed`, the authored SVG-count to equal the published Slide count, and the PPTX to pass in-memory ZIP-integrity. On failure, repair the owning SVG and rerun this command; do not-create planning or validation artifacts.--```markdown-## ✅ Quick Test Complete--- [x] Requested SVG pages exist under `svg_output/`-- [x] One native PPTX exists under `exports/` or the explicit output path-- [x] No normal-pipeline artifacts were created-- [ ] **Next**: Report the PPTX path-```diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.mdindex a66dd2ce..2eb78a4a 100644--- a/skills/ppt-master/workflows/routing.md+++ b/skills/ppt-master/workflows/routing.md@@ -30,7 +30,7 @@ route selection. After selection, the route authority owns execution.| Route | Request shape | Authority | Preconditions | Mutation model | Output contract ||---|---|---|---|---|---|-| Generate PPTX | Create a new presentation; regenerate an existing deck visually; use source material or a topic; optionally apply an explicit template workspace | [`generate-pptx`](./generate-pptx.md) | Source facts exist or the topic-research stage can gather them; explicit `quick-test` supplies self-contained test content | Author new SVG pages and export a new PPTX | Default pipeline: project with `design_spec.md`, `spec_lock.md`, `svg_output/`, `validation/`, and `exports/`; explicit `quick-test`: only `svg_output/` plus one PPTX |+| Generate PPTX | Create a new presentation; regenerate an existing deck visually; use source material or a topic; optionally apply an explicit template workspace | [`generate-pptx`](./generate-pptx.md) | Source facts exist or the topic-research stage can gather them; explicit `quick-generate` supplies fact-sufficient self-contained content | Author new SVG pages and export a new PPTX | Default pipeline: project with `design_spec.md`, `spec_lock.md`, `svg_output/`, `validation/`, and `exports/`; explicit `quick-generate`: only `svg_output/` plus one PPTX || Create Template | Create a reusable brand/layout/deck template from one or more PPTX/SVG files, images/PDFs, direct or file-based text, documents/websites, brand assets, or a mixed reference bundle | [`create-template`](./create-template.md) | A reusable-template request exists; reference material is optional, and project scope additionally requires an initialized target project | Author a new portable workspace; never modify any reference file in place | Workspace with required `templates/`, optional `images/` / `icons/`, and optional review `exports/` || Fill Native PPTX | Use a raw PPTX's native slide shells and replace/fill content | [`template-fill-pptx`](./template-fill-pptx.md) | Source PPTX plus new material/topic | Clone and patch PPTX through OOXML; no SVG pipeline | New filled PPTX in project `exports/` || Enhance Native PPTX | Keep a finished PPTX's visible slides stable while adding notes, audio, timings, or transitions | [`native-enhance-pptx`](./native-enhance-pptx.md) | Finished source PPTX exists | Append/update scoped OOXML parts; no slide regeneration | New enhanced PPTX in project `exports/` |@@ -41,7 +41,7 @@ route selection. After selection, the route authority owns execution.| Request condition | Generate-route behavior ||---|---|-| Explicit disposable test intent + explicit quick/fast mode + small fixed roster of self-contained slides | Activate [`quick-test`](./profiles/quick-test.md) inside Generate PPTX; author SVG pages and run the test-only direct exporter without entering normal Steps 1–7 |+| Explicit quick/fast generation or direct SVG-to-PPTX intent + fact-sufficient self-contained content | Activate [`quick-generate`](./profiles/quick-generate.md) inside Generate PPTX; decide the page structure in active context, skip Strategist and confirmation, author SVG pages, and run the direct exporter without entering default Steps 1–7 || Topic only, or supplied sources leave planning-critical factual gaps | Run [`topic-research`](./stages/topic-research.md) inside [`generate-pptx`](./generate-pptx.md) Step 1: immediately for topic-only input, or after conversion and reading for source-backed input; research only the identified gaps, then continue Step 2 || 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; use the default Generate pipeline || 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 |@@ -58,11 +58,11 @@ route selection. After selection, the route authority owns execution.**Hard rule — profile, not fifth route**: The 1:1 beautify behavior uses the same Strategist → Executor → SVG export lifecycle as Generate PPTX. It changes content/page invariants; it does not define a separate artifact lifecycle.-**Hard rule — test profile, not a release shortcut**: `quick-test` stays inside-Generate PPTX but owns a test-only SVG → PPTX short circuit. A small page count-alone never activates it, and any reusable, factual, source-backed,-template-backed, asset-dependent, or package-behavior request stays on the-normal Generate pipeline.+**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. Requests that require conversion,+research, templates, asset acquisition, native data objects, or additional+package behavior stay on the default Generate pipeline.---