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
refactor(quick-generate): make the runtime profile self-contained
hugohe36c90c9990b9f
diff --git a/AGENTS.md b/AGENTS.mdindex 3aef1cb9..8ed378a1 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -2,15 +2,15 @@This file is the project entry point for general AI agents.-**You MUST read [`skills/ppt-master/SKILL.md`](skills/ppt-master/SKILL.md) before any PPT generation task or repo modification.** It owns global execution discipline and points to the route selector; after routing, the selected route authority owns its steps, gates, and commands. The rest of this file only points to where related material lives.+**You MUST read [`skills/ppt-master/SKILL.md`](skills/ppt-master/SKILL.md) before any PPT generation task or repo modification.** It owns global execution discipline and points to the route selector; after routing, the selected runtime authority owns its steps, gates, and commands. The rest of this file only points to where related material lives.## Project Overview-PPT Master turns source material into natively editable DrawingML PPTX. Generate owns the default Strategist → Image_Generator → Executor pipeline and an explicit Quick profile without a separate strategy/confirmation phase.+PPT Master turns source material into natively editable DrawingML PPTX. Generate contains two mutually exclusive runtime paths: the default Strategist → Image_Generator → Executor pipeline and the self-contained Quick profile without a separate strategy/confirmation phase.**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.+- Topic-only or fact-insufficient inputs run [`topic-research`](skills/ppt-master/workflows/stages/topic-research.md) inside the selected Generate profile's source intake; facts only, no images.- Default Generate prepares template candidates internally in Step 3, then confirms the communication contract and free-design/template choice together in Stage 1. Template content stays unread until that confirmation; selected roots are installed before template-aware Stage 2. Quick skips this interaction.- 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 template workspace; run [`create-template`](skills/ppt-master/workflows/create-template.md) first and return with the generated workspace root as a Stage-1 candidate. Never add Master/Layout structure directly to an existing PPTX/SVG; generate new structured SVG pages from the workspace.@@ -40,7 +40,7 @@ PPT Master turns source material into natively editable DrawingML PPTX. Generate## Command Quick Reference-Convenience summary only — route selection starts in [`SKILL.md`](skills/ppt-master/SKILL.md); the full SVG-generation workflow is [`generate-pptx.md`](skills/ppt-master/workflows/generate-pptx.md).+Convenience summary only — route selection starts in [`SKILL.md`](skills/ppt-master/SKILL.md); Default/Beautify use [`generate-pptx.md`](skills/ppt-master/workflows/generate-pptx.md), while explicit Quick uses [`quick-generate.md`](skills/ppt-master/workflows/profiles/quick-generate.md) directly.```bash# Source content conversiondiff --git a/docs/technical-design.md b/docs/technical-design.mdindex 8d33c6d1..f95b174f 100644--- a/docs/technical-design.md+++ b/docs/technical-design.md@@ -48,7 +48,10 @@ The diagram below covers the default Generate PPTX lifecycle, including its`beautify-pptx` profile. The explicit `quick-generate` profile stays inside thesame 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.+run as needed; one lockless final quality gate remains mandatory. Routing loads+these runtime authorities independently: Default/Beautify read+`generate-pptx.md`, while Quick reads only `quick-generate.md`; neither profile+loads the other's procedure.Create Template has its own workspace lifecycle, while Fill Native PPTX andEnhance Native PPTX operate directly on OOXML; the route table later in thisdocument covers all four.@@ -490,7 +493,7 @@ choice.## Execution Discipline-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.+Generate routing selects one runtime authority before loading its procedure: [`workflows/generate-pptx.md`](../skills/ppt-master/workflows/generate-pptx.md) owns the Default Step 1–7 sequence and its Beautify overlay, while [`quick-generate.md`](../skills/ppt-master/workflows/profiles/quick-generate.md) owns the self-contained Quick lifecycle. [`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.diff --git a/docs/zh/technical-design.md b/docs/zh/technical-design.mdindex 21768305..4715f2ab 100644--- a/docs/zh/technical-design.md+++ b/docs/zh/technical-design.md@@ -40,7 +40,7 @@ PPT Master 不以“任意 SVG 都能转成 PPTX”为目标。`svg_output/` 使## Generate PPTX 路线架构-下图描述 Generate PPTX 的默认生命周期,也包含其 `beautify-pptx` profile。显式 `quick-generate` profile 仍属于同一路线,但只绕过独立的规划 / 确认、首屏 gate 与预览终稿化;来源理解和资源准备仍按需运行,一次无锁最终质量门始终保留。Create Template 有独立的工作区生命周期;Fill Native PPTX 与 Enhance Native PPTX 直接操作 OOXML。本文后续路线表会覆盖全部四条顶层路线。+下图描述 Generate PPTX 的默认生命周期,也包含其 `beautify-pptx` profile。显式 `quick-generate` profile 仍属于同一路线,但只绕过独立的规划 / 确认、首屏 gate 与预览终稿化;来源理解和资源准备仍按需运行,一次无锁最终质量门始终保留。路由会独立加载两套运行时权威:Default/Beautify 读取 `generate-pptx.md`,Quick 只读取 `quick-generate.md`,双方都不加载对方的流程。Create Template 有独立的工作区生命周期;Fill Native PPTX 与 Enhance Native PPTX 直接操作 OOXML。本文后续路线表会覆盖全部四条顶层路线。```用户输入 (PDF/DOCX/XLSX/PPTX/URL/Markdown/主题文本)@@ -431,7 +431,7 @@ Stage-1 沟通推荐的编写不得读取这些候选或任何模板内容。UI## 执行纪律-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 及其 Beautify 叠加规则,[`quick-generate.md`](../../skills/ppt-master/workflows/profiles/quick-generate.md) 拥有自足的 Quick 生命周期;[`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。本节不复制这些规则。diff --git a/skills/ppt-master/SKILL.md b/skills/ppt-master/SKILL.mdindex faa80344..60cbe96d 100644--- a/skills/ppt-master/SKILL.md+++ b/skills/ppt-master/SKILL.md@@ -26,17 +26,24 @@ PPT Master is a routed presentation workflow. This entry owns global execution dnon-zero result stops the Skill immediately; do not inspect, repair, orbypass the integrity gate.3. Read [`workflows/routing.md`](workflows/routing.md).-4. Select exactly one top-level route from the routing authority.-5. Read only that route's authority and its explicitly triggered supporting documents.+4. Select exactly one top-level route and its active profile from the routing+ authority.+5. Read only the resulting runtime authority and its explicitly triggered+ supporting documents.-| Selected route | Runtime authority |+| Selected route / profile | Runtime authority ||---|---|-| Generate PPTX | [`workflows/generate-pptx.md`](workflows/generate-pptx.md) |+| Generate PPTX — Default or Beautify | [`workflows/generate-pptx.md`](workflows/generate-pptx.md); Beautify additionally loads [`workflows/profiles/beautify-pptx.md`](workflows/profiles/beautify-pptx.md) |+| Generate PPTX — explicit Quick | [`workflows/profiles/quick-generate.md`](workflows/profiles/quick-generate.md) || Create Template | [`workflows/create-template.md`](workflows/create-template.md) || Fill Native PPTX | [`workflows/template-fill-pptx.md`](workflows/template-fill-pptx.md) || Enhance Native PPTX | [`workflows/native-enhance-pptx.md`](workflows/native-enhance-pptx.md) |-**Hard rule — selected authority only**: Do not load another top-level route's procedure after routing. Profiles, stages, governance files, and child workflows refine the selected route; they never compete with it.+**Hard rule — selected authority only**: Do not load another top-level route's+procedure after routing. Default/Beautify and Quick are mutually exclusive+Generate runtime authorities: neither loads the other's procedure. Profiles,+stages, governance files, and child workflows refine one selected route; they+never compete with it.---diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.jsonindex ec50ea96..e7bc8f1d 100644--- a/skills/ppt-master/scripts/prompt_audit_manifest.json+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json@@ -187,13 +187,12 @@"max_tokens": 70000},"route.generate.quick-generate": {- "description": "Explicit one-pass Generate path with active-context mode/style selection, conditional source/resource preparation, and complete flat SVG visual-construction authorities.",+ "description": "Self-contained one-pass Generate profile with source intake, active-context mode/style selection, conditional resource preparation, and complete flat SVG visual-construction authorities.","scope": "cumulative","include": ["bootstrap.routing"],"files": [- "skills/ppt-master/workflows/generate-pptx.md","skills/ppt-master/workflows/profiles/quick-generate.md","skills/ppt-master/references/artifact-ownership.md","skills/ppt-master/references/shared-standards-core.md",@@ -1022,10 +1021,15 @@"to": "skills/ppt-master/workflows/routing.md"},{- "concern": "generate-workflow",+ "concern": "default-generate-workflow","from": "skills/ppt-master/workflows/routing.md","to": "skills/ppt-master/workflows/generate-pptx.md"},+ {+ "concern": "quick-generate-workflow",+ "from": "skills/ppt-master/workflows/routing.md",+ "to": "skills/ppt-master/workflows/profiles/quick-generate.md"+ },{"concern": "failure-policy","from": "skills/ppt-master/workflows/generate-pptx.md",diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.mdindex a7302fab..2b14b1c3 100644--- a/skills/ppt-master/workflows/generate-pptx.md+++ b/skills/ppt-master/workflows/generate-pptx.md@@ -1,10 +1,12 @@----description: Generate PPTX route authority for source intake, planning, SVG authoring, quality gates, and native PPTX export.+description: Default Generate PPTX authority for source intake, planning, SVG authoring, quality gates, and native PPTX export.---# Generate PPTX Route-> Load only after [`routing.md`](./routing.md) selects Generate PPTX. This file owns the route's Step 1–7 sequence, gates, role switching, and mandatory commands.+> Load only after [`routing.md`](./routing.md) selects Default Generate or its+> Beautify profile. This file owns that runtime's Step 1–7 sequence, gates, role+> switching, and mandatory commands. Explicit Quick loads its own profile instead.**Default Core Pipeline**: `Initial Materials → [Fact Research] → Create Project → Template Candidate Preparation → Stage-1 Communication + Template Confirmation → [Template Installation] → Stage-2 Solution → [Image Acquisition] → Executor Live Preview → Quality Check → Post-processing → Export`@@ -15,34 +17,9 @@ 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 Generate Profile Short Circuit--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 one active context, then-hand-authors SVG, runs any selected capability-specific preparation, passes 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`; it creates no-resumable design history, so context loss restarts the Quick run.--Quick never enters Steps 3–4. When the request supplies at most one exact current-workspace root for each Brand/Style/Layout/Deck kind, or the current-conversation carries an exact Create Template handoff, Quick runs-[`apply-template-workspace`](./stages/apply-template-workspace.md) directly and-uses the installed project-local state during authoring. With no exact root it-uses free design. It never launches `confirm_ui/server.py`, reads the template-catalog to choose on the user's behalf, or creates template-selection receipts;-a bare template name, brand mention, or style description remains brief text.--**Hard rule — no implicit capability downgrade or page cap**: page count neither-selects nor blocks quick generation. Source preparation, images, icons, native-shapes, charts/tables, formulas, mode/style references, and their triggered-operational manifests remain available. All exporter capabilities remain-available when requested or agent-selected; use their existing prerequisites.-Structured Master/Layout template compilation still requires the default-lock-backed pipeline; Quick applies templates while authoring complete flat-pages.+**Profile boundary**: Explicit Quick is selected before runtime authority+loading and never enters this file. Default and Beautify do not load or apply+the Quick profile.### SVG Page-Design Boundarydiff --git a/skills/ppt-master/workflows/profiles/quick-generate.md b/skills/ppt-master/workflows/profiles/quick-generate.mdindex 1e3c3da0..38815cd7 100644--- a/skills/ppt-master/workflows/profiles/quick-generate.md+++ b/skills/ppt-master/workflows/profiles/quick-generate.md@@ -29,6 +29,11 @@ Page count alone never activates or blocks this profile.| Traceability | Operational resource manifests, checker reports, postflight, and bounded Python command/outcome audit entries may remain, but they do not record the AI's design reasoning or form a resumable generation history || 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` |+**Artifact ownership**: follow+[`artifact-ownership.md`](../../references/artifact-ownership.md) for source,+fact, author, derived, and regeneration boundaries. Quick changes the planning+handoff, not those artifact roles.+**Hard rule — speed removes interaction and durable planning, not capability**:all ordinary source, research, visual-carrier, resource-preparation, analysis,authoring, and export capabilities remain available when they serve the deck.@@ -68,8 +73,35 @@ point; a before-authoring signal always overrides a before-export-only timing.## 2. Source and Resource Preparation-Run [`generate-pptx.md`](../generate-pptx.md) Step 1 when applicable. Before-initialization, resolve exactly one of these branches:+Prepare source facts before initialization:++| Input | Action |+|---|---|+| Topic or requirements without supporting facts | Run [`topic-research`](../stages/topic-research.md) immediately and retain its Markdown supplement plus fact-provenance JSON for import |+| PDF / DOCX / Office document / XLSX / XLSM / PPTX / EPUB / HTML / LaTeX / RST / web URL | Run `python3 ${SKILL_DIR}/scripts/source_to_md.py <file_or_URL_or_dir> [<file_or_URL_or_dir> ...]` |+| CSV / TSV | Read directly as a plain-text table source |+| Markdown or direct conversation text | Read directly |++The conversion dispatcher writes standard Markdown plus its conversion profile+beside each local source by default. Use `-t <type>` only when detection is+ambiguous and `-o` only for a required output path; with several or directory+inputs, `-o` names an output directory. A PPTX is converted to Markdown here and+receives its project analysis during the import step below.++After reading every direct and converted source, assess factual sufficiency:++| Material state | Action |+|---|---|+| The requested outcome is supported | Continue |+| A required externally verifiable claim remains unsupported | Run [`topic-research`](../stages/topic-research.md) for those gaps only |+| Closed corpus / source-only / no external enrichment | Stay within the supplied material |++**Sufficiency test**: research only when the requested outcome would otherwise+require inventing, omitting, or leaving unsupported an externally verifiable+claim. File presence or length does not establish sufficiency. Research gathers+facts only; image acquisition remains part of the resource preparation below.++Before initialization, resolve exactly one template branch:- **Direct template application**: one or more exact current workspace rootswere supplied in the request, or Create Template returned an exact validated@@ -99,14 +131,45 @@ It creates `svg_output/` plus the coldthis command, run project-scoped Python tools directly; their shared CLIbootstrap records command envelopes, material tagged outcomes, bounded statussamples, and omission counts. A concise manual entry is allowed only for a-material non-Python audit detail under Generate Step 2's selective policy.+material stage handoff, rework reason, user-approved exception, or manual+recovery choice that has no owning command output; do not record routine page+progress, artifact contents, or private reasoning.Never read the log during ordinary Quick execution; open it only for anexplicit user-requested run review. Addcapability inputs only when triggered; later tools create `exports/` and the-default-path `backup/`. With source files, continue with Step 2-`import-sources`; it creates the triggered input directories. Never scaffold a-Design Spec or lock. Use a new path, or verify that an existing path's-`svg_output/` is empty; Quick ignores any existing `design_spec.md` or+default-path `backup/`.++With file-based sources, import the original inputs, converted outputs, and any+research pair together:++```bash+python3 ${SKILL_DIR}/scripts/project_manager.py import-sources \+ <project_path> <source_files_or_dirs...> [<converted_outputs...>] \+ [projects/<research_slug>.md projects/<research_slug>.facts.json]+```++Only inputs already under the repository's `projects/` tree move into the+target project; every external path is copied and remains untouched. Use+`--copy` when a projects-local input must also remain in place. When conversion+wrote Markdown beside the original source, pass that source path or directory+once; when `-o` wrote it elsewhere, pass both locations. Direct supported bitmap+inputs are archived under `sources/` and copied collision-safely into `images/`.++For each imported PPTX, `import-sources` automatically writes+`analysis/<stem>.identity.json`, `analysis/<stem>.slide_library.json`, and the+multi-deck `analysis/source_profile.json` index. Read that index as source facts+and open a per-deck artifact only when the current task needs its additional+detail; these facts are recommendations, not replica constraints. Distinct PPTX+stems may coexist, and re-importing one stem replaces only that deck's entry.++Conversion companion manifests may place extracted SVG/EMF/WMF assets into the+project resource flow. Preserve EMF/WMF as vector references and never convert+them to PNG; browser preview may be blank while native PPTX export remains the+source of truth. Standalone SVG/EMF/WMF inputs remain source assets unless such+a manifest supplies their display metadata.++Never scaffold a Design Spec or lock. Use a new path, or verify that an existing+path's `svg_output/` is empty; Quick ignores any existing `design_spec.md` or`spec_lock.md`.The audit log is an operational tool record only. It does not capture direct@@ -177,6 +240,12 @@ Prepare only the resource paths needed by the decided pages:| Illustration slice | Generate or obtain the parent sheet, run `slice_images.py`, and place only the resulting element files || Data chart/table | Keep source values and the chosen page treatment in active context; load the chart/table authorities in §3 before drawing and write native replacement metadata only when selected |+**Image inspection boundary**: acquisition-time suitability review follows the+owning AI/web/slice reference. Once resources reach terminal status, SVG+authoring follows `executor-image.md`'s narrow placement inspection: inspect only+one specifically ambiguous `Existing`/`Sourced` asset and never routinely reopen+`Generated` outputs.+After image resources change, run `analyze_images.py` so`analysis/image_analysis.csv` reflects the files that SVG authoring will use.Operational manifests and provenance are resource truth, not a hidden designdiff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.mdindex 300064c1..50c13caf 100644--- a/skills/ppt-master/workflows/routing.md+++ b/skills/ppt-master/workflows/routing.md@@ -8,7 +8,7 @@ Route selection authority for PPT Master. Select exactly one top-level route, th**Hard rule**: If this file conflicts with a route summary elsewhere in theSkill package or in a repository-level user-facing document, this file wins for-route selection. After selection, the route authority owns execution.+route selection. After selection, the active runtime authority owns execution.---@@ -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 select a registered library template or supply an explicit workspace | [`generate-pptx`](./generate-pptx.md) | Source facts exist or research can gather them; explicit quick intent activates its profile | Author new SVG pages and export a new PPTX | Default: spec, lock, SVG, validation, and PPTX; Quick: optional source/resource artifacts, no spec/lock, SVG, and one PPTX |+| Generate PPTX | Create a new presentation; regenerate an existing deck visually; use source material or a topic; optionally select a registered library template or supply an explicit workspace | Default/Beautify: [`generate-pptx`](./generate-pptx.md); explicit Quick: [`quick-generate`](./profiles/quick-generate.md) | Source facts exist or research can gather them; explicit quick intent activates its profile | Author new SVG pages and export a new PPTX | Default: spec, lock, SVG, validation, and PPTX; Quick: optional source/resource artifacts, no spec/lock, SVG, and one PPTX || Create Template | Create a reusable brand/style/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,9 +41,9 @@ 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, directly apply at most one exact workspace root per kind supplied for this run, otherwise use free design, omit Strategist/Confirm UI/spec/lock, hand-author SVG, run the lockless final checker, and export the final PPTX |+| Explicit quick/fast, skip-strategy, or direct SVG-to-PPTX intent | Load [`quick-generate`](./profiles/quick-generate.md) directly without loading `generate-pptx.md`: prepare sources/resources as needed, let the current agent decide without interaction, directly apply at most one exact workspace root per kind supplied for this run, otherwise use free design, omit Strategist/Confirm UI/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 may be split, merged, dropped, reordered, or re-outlined | Treat the PPTX as source content through the selected Generate authority's source 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 || Default Generate reaches planning | Step 3 prepares template candidates without interaction. Stage 1 then confirms the communication contract and free-design/template choice together; only a confirmed non-free choice runs [`apply-template-workspace`](./stages/apply-template-workspace.md) before Stage 2 || Explicit current brand/style/layout/deck workspace root | Default Generate preserves the exact path as a Stage-1 template candidate; Quick Generate validates and installs it directly without Steps 3–4 or Confirm UI. Classify it as `library` only when its normalized root exactly matches a registered index entry; otherwise retain `explicit`. Consume the workspace root, never only its inner `templates/` directory |@@ -65,7 +65,9 @@ count alone never activates or blocks it. Conversion, bounded research, andproject-local resources remain available. Package capabilities may be requestedor agent-selected. Quick may consume exact Brand/Style/Layout/Deck workspaces asflat authoring inputs; compiling reusable Master/Layout/placeholder structure-still requires the default lock-backed Generate pipeline.+still requires the default lock-backed Generate pipeline. Once selected, Quick+is the complete runtime procedure and never loads `generate-pptx.md`; Default+and Beautify never load `quick-generate.md`.---diff --git a/skills/ppt-master/workflows/stages/topic-research.md b/skills/ppt-master/workflows/stages/topic-research.mdindex 3d8d77e7..17a5afbd 100644--- a/skills/ppt-master/workflows/stages/topic-research.md+++ b/skills/ppt-master/workflows/stages/topic-research.md@@ -4,7 +4,12 @@ description: Generate source-intake stage that fills externally verifiable factu# Topic Research Stage-> Factual preparation inside [`generate-pptx`](../generate-pptx.md) source intake. Default Generate hands its output to Strategist; Quick Generate's main agent consumes the same output. Run immediately for topic-only input, or after supplied material is converted and read when it leaves planning-critical factual gaps. Output is a research supplement plus stable fact provenance for project import.+> Factual preparation inside the active Generate profile's source intake.+> Default Generate hands its output to Strategist; Quick Generate's main agent+> consumes the same output. Run immediately for topic-only input, or after+> supplied material is converted and read when it leaves planning-critical+> factual gaps. Output is a research supplement plus stable fact provenance for+> project import.This stage supplies facts needed to build the requested deck. It does not select,download, or generate images. Default Generate resolves image selection in the@@ -18,7 +23,7 @@ phase without adding a confirmation gate.|---|---|| Topic or requirements with no supporting facts | Research the factual baseline needed for the requested outcome || Supplied files or chat content cover only part of the requested outcome | After conversion and reading, research only the identified externally verifiable gaps |-| Supplied material already supports the requested outcome | Skip this stage and continue Generate Step 1 |+| Supplied material already supports the requested outcome | Skip this stage and continue the active Generate profile's source preparation || User requires a closed corpus, source-only transformation, or no external enrichment | Skip this stage and keep planning within supplied material |**Sufficiency test**: a gap exists when the active content owner would otherwise need to invent, omit, or leave unsupported an externally verifiable claim required by the user's requested outcome. File presence, source length, and a generic topic taxonomy do not decide sufficiency.@@ -136,7 +141,8 @@ IDs are immutable within the file. Correct a claim under the same ID; never reus## Hand-off-Import the research supplement and provenance alongside any user-supplied sources in Generate Step 2:+Import the research supplement and provenance alongside any user-supplied+sources through the active profile's source intake:```bashpython3 ${SKILL_DIR}/scripts/project_manager.py import-sources projects/<project_name> [<source_paths...>] projects/<research_slug>.md projects/<research_slug>.facts.json@@ -155,5 +161,5 @@ active-context content, design, and resource decisions.- [x] Fact provenance: `projects/<research_slug>.facts.json` (N external facts)- [x] Artifact contract validated: `## Research Brief`, `## Sources`, `ppt-master.fact-provenance.v1`, unique sequential IDs, and Markdown/JSON agreement- [x] No images acquired inside this factual-research stage-- [ ] **Next**: return to [`generate-pptx`](../generate-pptx.md), import all source artifacts in Step 2, then fully read the imported research pair before planning or direct SVG authoring+- [ ] **Next**: Default returns to [`generate-pptx`](../generate-pptx.md) Step 2; Quick returns to [`quick-generate`](../profiles/quick-generate.md) §2. Import all source artifacts, then fully read the imported research pair before planning or direct SVG authoring```