Skip to content

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

feat(quick-generate): apply supplied template workspaces directly

hugohe35cead2a3e20b
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 02050532..50d14f81 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -83,6 +83,13 @@ You: Turn this into a deck, skip the confirmation, about 8 pages, dark corporate
**Whatever you state explicitly is followed; whatever you leave unspecified the agent decides directly, without coming back to ask.** The page count and the look in the second example still hold — quick mode drops the round trip, not your say. State nothing, and the agent decides everything.
+Quick mode never opens the Confirm UI template selector. Give it up to one exact
+Brand / Style / Layout / Deck workspace root per kind and it validates,
+installs, and uses them directly; give it no exact root and it uses free design.
+A bare template name or style phrase is still only a design brief. Quick keeps
+its lockless flat export, so Layout / Deck prototypes guide the authored pages
+but do not compile into reusable native Master / Layout objects.
+
It does not skip preparation: source conversion, research on identified factual gaps, and image / icon / formula preparation still run as needed. If a required asset is missing, it still stops and asks you for it instead of substituting unrelated material.
Because the whole planning phase no longer happens (Strategist analysis, `design_spec.md` / `spec_lock.md` authoring, the staged confirmation round trip), token usage is materially lower than the default flow. Per-page SVG authoring is unchanged, so this is neither a wall-clock promise nor a promise of quality equivalence with the default flow.
diff --git a/docs/templates-guide.md b/docs/templates-guide.md
index bef443f5..1c31d0f1 100644
--- a/docs/templates-guide.md
+++ b/docs/templates-guide.md
@@ -54,6 +54,12 @@ The two rules that prevent most mistakes:
The default confirmation page opens an independent **Step-3 template-selection phase before Stage 1**. It offers free design, registered Brand/Style/Layout/Deck workspaces, and any exact workspace roots already supplied for the run. It does not infer a recommendation from the topic: the user makes the selection explicitly.
+> **Quick Generate exception:** Quick never opens that page. Up to one exact
+> workspace root per kind supplied in the request is validated, installed, and
+> used directly; no exact root means free design. Bare names still do not
+> resolve. Quick remains a lockless flat export, so Layout/Deck prototypes are
+> authoring inputs rather than reusable native Master/Layout output.
+
### How to enter the template flow
On the default page, choose free design or compose templates through five compact dropdowns: one each for registered Brand, Style, Layout, and Deck workspaces, plus one for exact roots supplied for this run. Each dropdown is single-select and includes `None`; the four registered kinds can be combined, and the specified-root channel contributes at most one workspace. The registered lists come only from the four kind indexes; the workflow never scans the template directories. You can also send an exact Brand/Style/Layout/Deck workspace root in chat before Step 3. Anywhere in the sentence is fine; the path just has to be unambiguous:
diff --git a/docs/zh/getting-started.md b/docs/zh/getting-started.md
index bdfded9f..f3a61278 100644
--- a/docs/zh/getting-started.md
+++ b/docs/zh/getting-started.md
@@ -83,6 +83,12 @@ Create Template 会分析参考材料,确认结果属于 Brand、Style、Layou
**你明确提的照做,你没提的 AI 直接定,不再回来问你。** 第二个例子里的页数和风格照样生效——快速模式省掉的是来回确认,不是你的话语权;什么都不提,才是全部交给 AI 决定。
+快速模式不会打开 Confirm UI 的模板选择页。每个 kind 最多给出一个精确的
+Brand / Style / Layout / Deck 工作区 root,它会直接校验、安装并使用;没有
+给出精确 root,就直接自由设计。只写模板名或风格词仍然只是设计说明。
+Quick 保持无锁 flat 导出,因此 Layout / Deck 原型会指导页面创作,但不会
+编译成可复用的原生 Master / Layout 对象。
+
它不跳过备料:来源转换、事实缺口研究、图片 / 图标 / 公式准备仍按需运行。必需素材缺失时它会停下来跟你要,不会拿无关材料顶替。
整个规划阶段不再发生(策略师分析、`design_spec.md` / `spec_lock.md` 落盘、分步确认往返),因此 token 消耗明显低于默认流程;逐页 SVG 生成的开销不变,所以这既不是耗时承诺,也不承诺与默认流程质量等价。
diff --git a/docs/zh/templates-guide.md b/docs/zh/templates-guide.md
index 3e9babc3..897adbb3 100644
--- a/docs/zh/templates-guide.md
+++ b/docs/zh/templates-guide.md
@@ -48,6 +48,11 @@ Theme、Slide Master、Slide Layout 与 Placeholder 是 PowerPoint 原生对象
默认确认页面会在 Stage 1 之前打开一个独立的 **Step 3 模板选择阶段**,同时提供自由设计、已注册的 Brand/Style/Layout/Deck,以及本次运行已明确给出的工作区根目录。它不会根据主题替用户推断推荐模板,选择必须由用户明确完成。
+> **快速模式例外:** Quick 不会打开这个页面。请求中每个 kind 最多一个精确
+> 工作区 root,会被直接校验、安装并使用;没有精确 root 就直接自由设计。
+> 裸模板名仍不会被解析。Quick 继续采用无锁 flat 导出,因此 Layout/Deck
+> 原型是页面创作输入,不会变成可复用的原生 Master/Layout 输出。
+
### 怎么触发模板流程
默认页面提供自由设计,以及五个紧凑下拉框:Brand、Style、Layout、Deck 各一个已注册工作区单选框,再加一个本次运行指定地址单选框。每个下拉框都有“无”;四类已注册模板可跨类型组合,指定地址最多选一个。已注册列表只来自四类索引,工作流不会扫描模板目录。也可以在 Generate PPTX 进入 Step 3 前,于对话里写出 Brand/Style/Layout/Deck 工作区根目录(位置不重要,只要明确即可):
diff --git a/skills/ppt-master/references/artifact-ownership.md b/skills/ppt-master/references/artifact-ownership.md
index 055a144d..e8e9c22b 100644
--- a/skills/ppt-master/references/artifact-ownership.md
+++ b/skills/ppt-master/references/artifact-ownership.md
@@ -8,9 +8,11 @@ profile may explicitly omit an artifact without erasing its facts.
**Quick Generate projection**: Quick omits confirmation, Design Spec, and lock.
Its current main agent reads source/analysis facts, keeps routine decisions in
active context, and prepares images/icons/formulas plus required manifests
-before SVG authoring. Those artifacts retain their factual/provenance roles.
-Quick writes the same final SVG quality provenance and package postflight as
-the default profile, but it does not create `svg_final/`.
+before SVG authoring. Exact template workspace roots supplied for the run are
+validated and installed directly; Quick reads only that project-local state and
+creates no Confirm UI selection artifacts. Those artifacts retain their
+factual/provenance roles. Quick writes the same final SVG quality provenance and
+package postflight as the default profile, but it does not create `svg_final/`.
---
@@ -34,7 +36,7 @@ the default profile, but it does not create `svg_final/`.
| `images/image_prompts.json`, `image_queries.json`, `image_sources.json`, `formula_manifest.json` | Conditional resource contracts | AI/web/formula execution status and provenance | Create only for a triggered path, including Quick. They guide preparation/attribution, never page design. |
| `icons/` | Prepared project icon pool | Bundled icons copied by `icon_sync.py` plus user-provided, template, imported, or custom icon SVGs | SVG authoring may use any icon in this project-local pool; `spec_lock.icons.inventory` records the default plan's bundled choices rather than an exhaustive whitelist. Exporter global fallback is legacy compatibility only. |
| `${SKILL_DIR}/templates/{brands,styles,layouts,decks}/*_index.json` | Library discovery indexes | The complete registered option source for Step-3 UI selection and chat listing | Read the four index files only; never scan kind directories to add options. Derive a library root from kind + entry id. Exact unregistered roots remain explicit inputs and never enter an index implicitly. |
-| `templates/` | Project template reference | Step 3 installed/fused specs, optional Layout/Deck SVG prototypes, and non-image assets | From Stage 2 onward, template-aware Strategist work and every later role read this project-local state only, never the library/external installation root. Strategist reads every installed template Design Spec and an actual SVG roster only for Layout/Deck; Brand and Style are intentionally roster-free. Continuous Executor reuses that context; fresh Executor reads the Design Spec once and each selected complete SVG, when any, only before first use or after its SHA changes. |
+| `templates/` | Project template reference | Default Step 3 or Quick direct-input installed/fused specs, optional Layout/Deck SVG prototypes, and non-image assets | Default template-aware Strategist work from Stage 2 onward, Quick's current agent before direct authoring, and every later role read this project-local state only, never the library/external installation root. The active planner reads every installed template Design Spec and an actual SVG roster only for Layout/Deck; Brand and Style are intentionally roster-free. Continuous Executor reuses that context; fresh Executor reads the Design Spec once and each selected complete SVG, when any, only before first use or after its SHA changes. |
| `templates/template_execution_manifest.json` (`v1`) + `templates/template_execution/*.text-slots.json` (`v2-min`) | Derived template index | Compact prototype/source-import summary plus per-prototype text-slot diagnostics; the sidecar integrity hash is tool-only | Materialization may publish these deterministic records, but page-context does not inject or require them and models do not read them during page authoring. The complete prototype SVG is the sole visual/template authority; never author from either JSON artifact. |
| `<import_workspace>/svg/` | Imported native-payload backing | Complete PPTX-derived metadata, hidden carriers, fallback evidence, and source structure | Keep immutable; create-template materialization may resolve a validated source ref against these files, but models do not edit or bulk-read them |
| `<import_workspace>/svg-flat/` | Optional complete-page verification backing | Self-contained visual composition generated only by explicit `--inheritance-mode both` | Keep immutable when requested; never use as authoring or materialization input |
@@ -43,7 +45,7 @@ the default profile, but it does not create `svg_final/`.
| `<import_workspace>/authoring-svg/authoring_manifest.json` | Tool-only authoring provenance contract | Per-document source/authoring hashes and document-local source-ref paths | Generated atomically with the IR; materialization validates it before reusing native payload; never load it into model context or duplicate raw payload here |
| `<import_workspace>/authoring-svg-flat/` | Optional complete-page verification IR | Self-contained page composition view with its own summary and provenance manifest | Generate only from an explicitly requested `svg-flat/`; use to verify composition, while layered `authoring-svg/` remains the canonical editable source |
| `<import_workspace>/icons/imported/` | Imported vector pool | One canonical copy of every factored vector subtree | Authoring SVGs reference `data-icon="imported/<name>"`; vector inventories retain source refs so expansion re-establishes IR identity |
-| `confirm_ui/template_options.json`, `template_selection.json`, `template_handoff.json` | Step-3 template phase | Agent-authored input, user-confirmed exact selection, and agent-authored installation/free-design completion receipt | The server builds library candidates only from the four indexes and binds selection/handoff hashes. Stage 1 is exposed only after the bound handoff and a fresh recommendation. Template choices never enter `result.json`. |
+| `confirm_ui/template_options.json`, `template_selection.json`, `template_handoff.json` | Default Step-3 template phase | Agent-authored input, user-confirmed exact selection, and agent-authored installation/free-design completion receipt | Default only: the server builds library candidates from the four indexes and binds selection/handoff hashes. Stage 1 is exposed only after the bound handoff and a fresh recommendation. Template choices never enter `result.json`. Quick creates none of these files. |
| `confirm_ui/recommendations.stage1.json`, `.stage2.json`, `.stage3.json` | Confirmation proposals | One Strategist-authored payload per communication/solution/production stage | Create these only after Step-3 template selection and installation closes. Template choice is not a Stage-1 field; Stage 2 may carry only `template_application`, which decides how to use the installed project-local template. Confirm UI selects the active file from `result.json`. The active, unconfirmed stage may be overwritten when the user requests a new recommendation; normal progression writes the next stage file and leaves confirmed earlier stages intact. Legacy `recommendations.json` is read only when no stage-specific file exists. |
| `confirm_ui/result.json` | Confirmation result | Persisted user-confirmed input evidence | Generate Step 4 reads the final object once into active context; Strategist consumes it completely into `design_spec.md`. Normal downstream work does not reopen it; fresh recovery may read it once when no retained final state exists. |
| `svg_output/` | Page-design author source | Main-agent handwritten SVG pages containing the complete visible design | Quality checker and native PPTX export read this as the canonical visual/page-layout source; templates and locks do not add missing visible objects at export |
@@ -79,7 +81,7 @@ the default profile, but it does not create `svg_final/`.
| Export source | The only supported generated-PPTX route reads `svg_output/` through the project SVG-to-DrawingML converter. A diagnostic `-s final` override does not change ownership or create a supported release route. |
| Shape-conversion boundary | PowerPoint's manual Convert-to-Shape operation on `svg_final/` is outside the project compatibility contract. |
| Confirmation | Final UI/chat confirmation overrides recommendations and is consumed once into `design_spec.md`. Enabled refinement applies arbitrary revisions there and requires approval; only then may active-decision fidelity release lock authoring. |
-| Template selection | Step 3 confirms free design or exact roots before Stage 1. Library candidates come only from the four `*_index.json` files; unregistered roots require explicit input. Every non-free selection runs the same validator/installer and becomes one project-local `templates/` state before Strategist reads it. Stage 2 owns use, not selection. |
+| Template selection | Default Step 3 confirms free design or exact roots before Stage 1; library candidates come only from the four `*_index.json` files, and unregistered roots require explicit input. Quick never enters that phase: at most one exact root per kind supplied for the run goes directly through the same validator/installer, while no exact root means free design. Every applied selection becomes one project-local `templates/` state before Default Stage 2 or Quick authoring reads it. |
| Proactive production outcomes | Resolve notes/animation/narration from explicit instruction → Stage 3 → defaults, then persist outcomes/provenance only in Design Spec §I. Explicit notes-off/audio-on applies Generate's dependency gate; Stage 3 animation `false` does not suppress a sidecar. |
**Forbidden - mixed ownership**: Do not copy chart values from Markdown into `analysis/` by hand, do not edit `svg_final/` as the source of a fix, do not edit imported lossless SVGs instead of their authoring IR, and do not treat `design_spec.md` prose as a replacement for `spec_lock.md`.
diff --git a/skills/ppt-master/scripts/docs/prompt_audit.md b/skills/ppt-master/scripts/docs/prompt_audit.md
index 4e971eb4..dc7d4cea 100644
--- a/skills/ppt-master/scripts/docs/prompt_audit.md
+++ b/skills/ppt-master/scripts/docs/prompt_audit.md
@@ -36,4 +36,4 @@ The manifest is audit-only (`audit_only: true`, `runtime_consumed: false`); it i
- **New corpus file** → when no existing category exemption matches it, the audit fails with `LOAD_COVERAGE_GAP` until you add it to the load sets that read it or exempt it with a one-line reason. Exempt only material that never enters role context (for example, a legacy tombstone, generated maintenance asset, maintainer-only doc, or license notice); represent conditional runtime reads as incremental load sets.
- **Intentional duplicate** → run `--json`, copy the finding's `kind`, `fingerprint`, and `paths` into `duplicates.accepted` with a reason. The acceptance identity is all three values, so separate path pairs with identical prose remain independently reviewable. Editing either reported raw block changes its fingerprint; stale acceptance fails with `DUPLICATE_ACCEPTED_STALE`. `--skip-near-duplicates` deliberately leaves accepted near pairs unchecked because that scan did not run.
- **Schema owner** → every configured field must have a definition signal in its declared owner. One grammar-like non-owner is enough to surface a candidate; split fields into separate owner entries when they belong to different artifacts.
-- **Budget ceilings** (`budget_policy: fixed_upper_bound`): budgets are stable, deliberately rounded limits rather than mirrors of the current token count. Establish a ceiling with roughly 10% working headroom and round it up in 250-token increments below 10k, 1k increments below 100k, or 5k increments from 100k upward; the manifest loader enforces those increments. Ordinary wording edits do not change the ceiling. Raise it only when a deliberate architecture-level scope expansion would otherwise cross it, then choose the next rounded limit with comparable headroom and record why in that change.
+- **Budget ceilings** (`budget_policy: fixed_upper_bound`): budgets are stable, deliberately rounded limits rather than mirrors of the current token count. Establish a new ceiling with roughly 10% working headroom and round it up in 250-token increments below 10k, 1k increments below 100k, or 5k increments from 100k upward; the manifest loader enforces those increments. Once set, do not raise or lower a passing ceiling, including to restore headroom after prompt growth. Raise it only after the current audit reports `BUDGET_CORPUS`, `BUDGET_FILE`, or `BUDGET_LOAD_SET` against that exact ceiling; then choose the next rounded limit with comparable headroom, record the overflow-triggering scope in the same change, and leave it unchanged until another actual overflow.
diff --git a/skills/ppt-master/scripts/prompt_audit_manifest.json b/skills/ppt-master/scripts/prompt_audit_manifest.json
index 2a192881..1f044584 100644
--- a/skills/ppt-master/scripts/prompt_audit_manifest.json
+++ b/skills/ppt-master/scripts/prompt_audit_manifest.json
@@ -34,7 +34,7 @@
"skills/ppt-master/templates/design_spec_reference.md": 3750,
"skills/ppt-master/templates/spec_lock_reference.md": 2750,
"skills/ppt-master/workflows/generate-pptx.md": 16000,
- "skills/ppt-master/workflows/stages/apply-template-workspace.md": 2750
+ "skills/ppt-master/workflows/stages/apply-template-workspace.md": 3500
},
"load_sets": {
"bootstrap.routing": {
@@ -187,7 +187,7 @@
"max_tokens": 70000
},
"route.generate.quick-generate": {
- "description": "Explicit non-interactive Generate path with conditional source/resource preparation and the complete SVG visual-construction authorities.",
+ "description": "Explicit non-interactive Generate path with conditional source/resource/template preparation and the complete flat SVG visual-construction authorities.",
"scope": "cumulative",
"include": [
"bootstrap.routing"
@@ -202,6 +202,16 @@
],
"max_tokens": 61000
},
+ "route.generate.quick-generate.template-fusion": {
+ "description": "Quick Generate with the maximum Brand, Style, Layout, and Deck exact-root fusion loaded for flat authoring.",
+ "scope": "cumulative",
+ "include": [
+ "route.generate.quick-generate",
+ "stage.generate.template.fusion-brand-style-layout-deck"
+ ],
+ "files": [],
+ "max_tokens": 80000
+ },
"route.generate.quick-generate.topic-research": {
"description": "Quick Generate with gap-targeted factual research before direct resource preparation and SVG authoring.",
"scope": "cumulative",
@@ -308,7 +318,7 @@
"max_tokens": 86000
},
"stage.generate.apply-template-workspace": {
- "description": "Conditional Step 3 workspace validation, installation, and fusion framework.",
+ "description": "Conditional Default Step 3 or Quick exact-root workspace validation, installation, and fusion framework.",
"scope": "incremental",
"files": [
"skills/ppt-master/workflows/stages/apply-template-workspace.md",
@@ -330,7 +340,7 @@
"load_event": "template-application"
}
],
- "max_tokens": 6500
+ "max_tokens": 7500
},
"stage.generate.template.style": {
"description": "Conditional roster-free Style workspace application.",
@@ -357,7 +367,7 @@
"load_event": "template-application"
}
],
- "max_tokens": 8000
+ "max_tokens": 9000
},
"stage.generate.template.deck": {
"description": "Conditional Deck workspace application with one selected Deck spec.",
@@ -373,7 +383,7 @@
"load_event": "template-application"
}
],
- "max_tokens": 7500
+ "max_tokens": 8500
},
"stage.generate.template.brand-two": {
"description": "Same-kind conflict path with two selected Brand specs.",
@@ -389,7 +399,7 @@
"load_event": "template-application"
}
],
- "max_tokens": 7500
+ "max_tokens": 8500
},
"stage.generate.template.fusion-brand-style-layout-deck": {
"description": "Maximum supported cross-kind fusion with Brand, Style, Layout, and Deck contracts.",
@@ -418,7 +428,7 @@
"load_event": "template-application"
}
],
- "max_tokens": 14000
+ "max_tokens": 16000
},
"route.generate.flat-no-image": {
"description": "Default fixed Generate-PPTX context with no image-acquisition role.",
@@ -985,6 +995,11 @@
"from": "skills/ppt-master/workflows/generate-pptx.md",
"to": "skills/ppt-master/workflows/stages/apply-template-workspace.md"
},
+ {
+ "concern": "quick-template-application",
+ "from": "skills/ppt-master/workflows/profiles/quick-generate.md",
+ "to": "skills/ppt-master/workflows/stages/apply-template-workspace.md"
+ },
{
"concern": "template-model",
"from": "skills/ppt-master/workflows/stages/apply-template-workspace.md",
diff --git a/skills/ppt-master/templates/README.md b/skills/ppt-master/templates/README.md
index 4d107b41..c8da6ff9 100644
--- a/skills/ppt-master/templates/README.md
+++ b/skills/ppt-master/templates/README.md
@@ -50,7 +50,9 @@ confirmation,
[`apply-template-workspace`](../workflows/stages/apply-template-workspace.md)
validates, fuses, and installs every selected workspace into the current
project before Stage 1 starts. Template-aware reading begins in Stage 2 from
-that project-local copy.
+that project-local copy. Quick Generate is the non-interactive exception: it
+never opens this selector, directly applies exact roots supplied for the run,
+and uses free design when no exact root exists.
## Orthogonal contracts
@@ -87,14 +89,15 @@ Style narrows this shared routing shape to `templates/design_spec.md` only and
does not carry asset or review payloads; initialized-project sibling scaffolding
may exist but is not Style input.
The conditional [`apply-template-workspace`](../workflows/stages/apply-template-workspace.md)
-stage owns installation and fusion during the independent Step-3 selection
-phase. Brand/Layout/Deck consume package-owned
+stage owns installation and fusion during the default Step-3 selection phase or
+the Quick exact-root branch. Brand/Layout/Deck consume package-owned
`templates/`, `images/`, and `icons/`; Style consumes only
`templates/design_spec.md` and ignores sibling project scaffolding. Every kind
ignores `exports/`. Compatible legacy-flat Brand/Layout/Deck packages remain
readable; Style has no legacy-flat form, and directory shape alone does not
-indicate legacy Master/Layout semantics. Strategist and all later consumers use
-the installed project-local files, never the original library or explicit root.
+indicate legacy Master/Layout semantics. Default Strategist, Quick's current
+agent, and all later consumers use the installed project-local files, never the
+original library or explicit root.
## Design specification references
diff --git a/skills/ppt-master/templates/brands/README.md b/skills/ppt-master/templates/brands/README.md
index b2c08c4c..b889c507 100644
--- a/skills/ppt-master/templates/brands/README.md
+++ b/skills/ppt-master/templates/brands/README.md
@@ -21,7 +21,9 @@ conditional
stage owns path normalization, portable-root installation, multi-kind fusion,
same-kind conflict resolution, and provenance before Stage 1. Template-aware
reading begins in Stage 2 from the installed project-local copy. This file owns
-only the Brand schema.
+only the Brand schema. Quick Generate never opens the selector: an exact Brand
+root supplied for the run enters the same stage directly, while no exact root
+leaves Quick in free design.
## Creating a new brand
diff --git a/skills/ppt-master/templates/decks/README.md b/skills/ppt-master/templates/decks/README.md
index 77d68542..3be72c1d 100644
--- a/skills/ppt-master/templates/decks/README.md
+++ b/skills/ppt-master/templates/decks/README.md
@@ -42,6 +42,10 @@ confirming an entry triggers the conditional
stage, which owns path normalization, compatibility checks, installation, and
fusion before Stage 1. Template-aware reading begins in Stage 2 from the
installed project-local copy.
+Quick Generate never opens the selector: an exact Deck root supplied for the
+run enters the same stage directly, while no exact root leaves Quick in free
+design. Quick uses the installed prototypes as flat authoring inputs; reusable
+native Master/Layout compilation remains a default lock-backed capability.
This file owns the Deck schema and application-context boundary. Chat discovery
reads the same index and returns exact roots; a bare ID never resolves
implicitly.
diff --git a/skills/ppt-master/templates/layouts/README.md b/skills/ppt-master/templates/layouts/README.md
index 65fd376a..33c05547 100644
--- a/skills/ppt-master/templates/layouts/README.md
+++ b/skills/ppt-master/templates/layouts/README.md
@@ -57,6 +57,10 @@ Choosing and confirming an entry triggers the conditional
stage, which owns path normalization, compatibility checks, installation, and
fusion before Stage 1. Template-aware reading begins in Stage 2 from the
installed project-local copy.
+Quick Generate never opens the selector: an exact Layout root supplied for the
+run enters the same stage directly, while no exact root leaves Quick in free
+design. Quick uses the installed prototypes as flat authoring inputs; reusable
+native Master/Layout compilation remains a default lock-backed capability.
This file owns the Layout schema and its identity/application boundary. Chat
discovery reads the same index and returns exact roots; a bare ID never resolves
implicitly.
diff --git a/skills/ppt-master/templates/styles/README.md b/skills/ppt-master/templates/styles/README.md
index 833cd5de..39028e1a 100644
--- a/skills/ppt-master/templates/styles/README.md
+++ b/skills/ppt-master/templates/styles/README.md
@@ -26,7 +26,10 @@ registered root may be labelled `library`; otherwise it remains `explicit`. A
consulting label or ordinary visual description remains a brief or catalog
signal and does not activate this workspace. Confirmation runs the
common installation/fusion stage before Stage 1; template-aware reading begins
-in Stage 2 from the project-local copy.
+in Stage 2 from the project-local copy. Quick Generate never opens the selector:
+an exact Style root supplied for the run enters the same stage directly, while
+no exact root leaves Quick in free design; its current agent reads the installed
+copy before authoring flat pages.
| Decision | Precedence |
|---|---|
diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.md
index 4942b8fa..e6aaaf7f 100644
--- a/skills/ppt-master/workflows/generate-pptx.md
+++ b/skills/ppt-master/workflows/generate-pptx.md
@@ -25,11 +25,21 @@ hand-authors SVG, runs one lockless final checker, and exports the final PPTX.
It skips Strategist, Confirm UI, Design Spec/lock, the first-page gate, and
`finalize_svg.py`.
+Quick never enters Step 3. 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 downgrade or page cap**: page count neither selects
nor blocks quick generation. Source preparation, images, icons, formulas, and
their manifests remain valid. All exporter capabilities remain available when
requested or agent-selected; use their existing prerequisites. Structured
-template reuse still requires the default lock-backed pipeline.
+Master/Layout template compilation still requires the default lock-backed
+pipeline; Quick applies templates while authoring complete flat pages.
### SVG Page-Design Boundary
@@ -145,6 +155,10 @@ Direct supported bitmap inputs follow both boundaries: the original is archived
### Step 3: Template Selection and Installation
+**Scope**: Default Generate only. Quick Generate resolves exact supplied roots
+or free design inside its profile and never enters this Step or launches Confirm
+UI.
+
🚧 **GATE**: Step 2 complete; the project workspace exists. Finish this phase before authoring or confirming Stage 1. Template selection is not part of the Stage-1 communication contract.
**Default UI phase**: When the selected confirmation surface is the page, open its template-selection phase first. Show one exclusive free-design choice, four single-select registered-workspace dropdowns (Brand / Style / Layout / Deck), and one single-select specified-root dropdown. Every dropdown has a `None` option. A non-empty dropdown exits free design; choosing free design clears all five dropdowns. Populate the registered dropdowns from exactly these discovery sources:
diff --git a/skills/ppt-master/workflows/index.md b/skills/ppt-master/workflows/index.md
index c77bf329..4d566a73 100644
--- a/skills/ppt-master/workflows/index.md
+++ b/skills/ppt-master/workflows/index.md
@@ -21,7 +21,7 @@ Maintainer-only inventory for adding, moving, or removing workflow documents. Ru
|---|---|---|---|
| `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 |
+| `apply-template-workspace` | Template-input stage | [`stages/apply-template-workspace.md`](./stages/apply-template-workspace.md) | Default Generate Step 3 or Quick direct exact-root input |
| `create-brand` | Template child workflow | [`create-template/create-brand.md`](./create-template/create-brand.md) | Create Template |
| `create-style` | Template child workflow | [`create-template/create-style.md`](./create-template/create-style.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.md
index c3875108..bf2bc163 100644
--- a/skills/ppt-master/workflows/profiles/quick-generate.md
+++ b/skills/ppt-master/workflows/profiles/quick-generate.md
@@ -21,8 +21,9 @@ Page count alone never activates or blocks this profile.
| Authority | Follow every explicit user requirement as stated; decide every unspecified choice directly without asking |
| Interaction | The current main agent decides content, design, resources, and implementation without Strategist, Confirm UI, or approval stops |
| Inputs | Any supported Generate input; convert/import sources and run bounded factual research when the input requires them |
+| Templates | Directly validate and install at most one exact workspace root per kind supplied for this run; when none are supplied, use free design without catalog selection or Confirm UI |
| Resources | Prepare every project-local image, icon, formula, and required provenance/manifest artifact before the referencing SVG is authored |
-| Planning artifacts | Do not create `design_spec.md`, `spec_lock.md`, confirmation payloads, or a second persisted strategy |
+| Planning artifacts | Do not author a root project `design_spec.md`, `spec_lock.md`, confirmation payloads, or a second persisted strategy; an installed `templates/design_spec.md` remains template input |
| Delivery | Hand-author the resolved SVG roster, run one lockless final checker, skip `finalize_svg.py`, and export the final native PPTX through `--quick-generate` |
**Hard rule — speed removes interaction, not material**: all ordinary source,
@@ -41,7 +42,7 @@ Pause only for user interruption or an unresolved hard prerequisite.
notes, custom object animations, and narration start off. The current agent may
enable any ordinary capability when the request or deck benefits; use its
normal inputs, flags, and prerequisites without asking for approval. Quick
-never creates or reads a Design Spec or lock to enable it.
+never creates or reads a root project Design Spec or lock to enable it.
**Mandatory — discover motion before deciding whether to load it**: scan this
compact gate once; do not load the full execution reference when the defaults
@@ -64,8 +65,26 @@ 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. Initialize
-the minimal workspace with:
+Run [`generate-pptx.md`](../generate-pptx.md) Step 1 when applicable. Before
+initialization, resolve exactly one of these branches:
+
+- **Direct template application**: one or more exact current workspace roots
+ were supplied in the request, or Create Template returned an exact validated
+ root in the current conversation. Accept at most one root per declared kind.
+ Before initialization, load
+ [`apply-template-workspace`](../stages/apply-template-workspace.md), normalize
+ each supplied root, read only the matching spec frontmatter needed to resolve
+ its kind/canvas, and run that stage's read-only schema/structured preflight.
+ Do not scan the library, fuzzy-match a name, or open a selector. Explicit user
+ canvas wins; otherwise use the selected structure owner (Layout before Deck)
+ canvas when present, then fall back to `ppt169`.
+- **Free design**: no exact root was supplied. Continue immediately with the
+ requested canvas or `ppt169`. A bare template name, brand mention, style
+ phrase, or vague request to choose a template is ordinary brief input, not a
+ workspace reference.
+
+Neither branch creates anything under `confirm_ui/` or executes
+`confirm_ui/server.py`. Initialize the minimal workspace with:
```bash
python3 ${SKILL_DIR}/scripts/project_manager.py init <project_name> \
@@ -80,6 +99,23 @@ 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`.
+For the direct-template branch, resume
+[`apply-template-workspace`](../stages/apply-template-workspace.md) after
+initialization against only the preflighted roots. The user's request is the
+selection authority; there is no template confirmation receipt or handoff. The
+stage installs and fuses the workspaces into `<project_path>/templates/` plus
+the project-local asset pools. All later reads use that installed state, never
+the original roots.
+
+Before writing P01, read the installed template spec once and, for Layout/Deck,
+inspect the relevant SVG prototypes. Resolve one transient application plan in
+active context: apply Brand identity, Style direction/method, the selected
+structure owner's useful prototype geometry, and Deck application context under
+the existing segment precedence. Follow explicit instructions about literal or
+visual-only use; otherwise decide which prototypes to use, skip, repeat,
+reorder, or adapt from the current content. Persist no second plan. If no
+template was installed, resolve the same design choices freely.
+
Before writing P01, resolve in active context:
- the slide roster, canvas, visual direction, palette, typography, and wording;
@@ -140,16 +176,23 @@ Use one zero-padded filename width sized for the resolved roster, such as
Never reuse pages from another run: the exporter publishes every SVG discovered
under `svg_output/`.
-**Canvas**: unless the user specifies another canvas, use `ppt169` with
-`viewBox="0 0 1280 720"`. For another requested registered format, load
+**Canvas**: use the canvas resolved in §2: explicit user choice, otherwise the
+selected Layout/Deck structure-owner canvas, otherwise `ppt169` with
+`viewBox="0 0 1280 720"`. For another 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 and all resource references in each SVG; set one root
+viewBox. Template canvas is a default, not a compatibility gate; an explicit
+user canvas may adapt the installed visual system. The first SVG establishes
+the export canvas; every remaining page must match it exactly.
+
+**Structure**: author flat, Slide-local SVG only, including when a Layout or
+Deck workspace is installed. In that branch, visibly realize the resolved
+template rules and prototype geometry in the complete pages; do not fall back to
+free design or merely explain how the template could be used. Include the
+complete visible page and all resource references in each SVG; set one root
`data-pptx-page-role` from `cover`, `toc`, `section`, `content`, or `ending`,
-and omit Master/Layout/layer/placeholder metadata.
+and omit Master/Layout/layer/placeholder metadata. A request that specifically
+requires reusable native Master/Layout/placeholder output is incompatible with
+the lockless Quick exporter and must use the default lock-backed profile.
**Typography**: name an installed concrete font family in the SVG; do not depend
on a lock or generated font asset.
@@ -203,6 +246,6 @@ or lock.
- [x] The lockless final SVG quality report passes and matches the current SVGs
- [x] Every selected optional export capability completed
- [x] One native PPTX exists under `exports/` or the explicit output path
-- [x] No Strategist, confirmation, Design Spec, or lock artifact was created
+- [x] No Strategist, confirmation, root project Design Spec, or lock artifact was created
- [ ] **Next**: Report the PPTX path
```
diff --git a/skills/ppt-master/workflows/routing.md b/skills/ppt-master/workflows/routing.md
index 9f7a1f6d..f10e6d78 100644
--- a/skills/ppt-master/workflows/routing.md
+++ b/skills/ppt-master/workflows/routing.md
@@ -41,12 +41,12 @@ route selection. After selection, the route authority owns execution.
| Request condition | Generate-route behavior |
|---|---|
-| Explicit quick/fast, skip-strategy, or direct SVG-to-PPTX intent | Activate [`quick-generate`](./profiles/quick-generate.md): prepare sources/resources as needed, let the current agent decide without interaction, omit Strategist/confirmation/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 | 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 |
| Topic only, or supplied sources leave planning-critical factual gaps | Run [`topic-research`](./stages/topic-research.md) inside the selected Generate profile's source preparation: immediately for topic-only input, or after conversion and reading for source-backed input; research only the identified gaps |
| Existing PPTX may be split, merged, dropped, reordered, or re-outlined | Treat the PPTX as source content through [`generate-pptx`](./generate-pptx.md) Step 1 and its PPTX intake; continue the default pipeline unless explicit Quick Generate intent selected that profile |
| Existing PPTX must preserve wording, page count, and page order 1:1 | Activate the [`beautify-pptx`](./profiles/beautify-pptx.md) profile inside the main pipeline |
| Default Generate reaches Step 3 | Complete the independent template-selection phase before Stage 1. The UI offers only index-registered library roots plus any user-supplied explicit roots; confirmed non-free selections run [`apply-template-workspace`](./stages/apply-template-workspace.md) |
-| Explicit current brand/style/layout/deck workspace root | Preserve the exact-path path through Step 3. 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 |
+| Explicit current brand/style/layout/deck workspace root | Default Generate preserves the exact-path path through Step 3; Quick Generate validates and installs it directly without Step 3 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 |
| Split-mode project resumes in a fresh chat | Run [`resume-execute`](./stages/resume-execute.md) inside the active Generate route |
| Existing generated project needs a deck-wide `colors.*` or universal `typography.font_family` substitution | Stay in Generate; load [`update_spec.py`](../scripts/docs/update_spec.md), honor its supported-key boundary, then rerun the final quality gate and Step 7 export |
| User explicitly requests spec refinement | Run [`refine-spec`](./stages/refine-spec.md) after Design Spec Gate 1 and before lock Gate 2 |
@@ -63,8 +63,9 @@ route selection. After selection, the route authority owns execution.
stays inside Generate PPTX but owns an explicit SVG → PPTX short circuit. Page
count alone never activates or blocks it. Conversion, bounded research, and
project-local resources remain available. Package capabilities may be requested
-or agent-selected. Structured template reuse requires the default lock-backed
-Generate pipeline.
+or agent-selected. Quick may consume exact Brand/Style/Layout/Deck workspaces as
+flat authoring inputs; compiling reusable Master/Layout/placeholder structure
+still requires the default lock-backed Generate pipeline.
---
diff --git a/skills/ppt-master/workflows/stages/apply-template-workspace.md b/skills/ppt-master/workflows/stages/apply-template-workspace.md
index 900fb87c..6a9fde0d 100644
--- a/skills/ppt-master/workflows/stages/apply-template-workspace.md
+++ b/skills/ppt-master/workflows/stages/apply-template-workspace.md
@@ -1,14 +1,19 @@
---
-description: Generate-PPTX Step-3 runbook for validating, installing, or fusing selected Brand, Style, Layout, and Deck workspaces.
+description: Generate-PPTX runbook for validating, installing, or fusing selected Brand, Style, Layout, and Deck workspaces.
---
# Apply Template Workspace Stage
-> Run only from [`generate-pptx.md`](../generate-pptx.md) Step 3 after the user confirms the dropdown-composed library/explicit workspace roots, or after Create Template hands off its exact validated root in the current conversation. Never load this stage for confirmed free design, a bare template name, a style description, or a brand mention. This stage applies a completed selection; it does not move template choice into Stage 1 or Stage 2.
+> Run from [`generate-pptx.md`](../generate-pptx.md) Step 3 after the user confirms the dropdown-composed library/explicit workspace roots, or directly from [`quick-generate`](../profiles/quick-generate.md) when the request supplies exact roots or Create Template hands off its exact validated root in the current conversation. Never load this stage for default confirmed free design, Quick with no exact root, a bare template name, a style description, or a brand mention. This stage applies a completed selection; it never chooses a template or moves template choice into Stage 1 or Stage 2.
## 1. Gate and Normalize Inputs
-🚧 **GATE**: Step-3 template selection is confirmed and every selected input resolves to one of these current contracts:
+🚧 **GATE**: Either the default Step-3 template selection is confirmed, or
+Quick received the exact roots directly from the user/current Create Template
+handoff. In Quick, that explicit input is the complete selection authority: do
+not launch Confirm UI or create `template_options.json`,
+`template_selection.json`, or `template_handoff.json`. Every selected input must
+resolve to one of these current contracts:
| Input shape | Spec and SVG source | Asset source |
|---|---|---|
@@ -32,7 +37,7 @@ valid without index membership; exact equality with a registered root may be
reported as `library`. The label changes discovery provenance only, never schema
validation, fusion precedence, or installation behavior.
-**Selection cardinality**: The default page permits one registered root per kind plus one explicit root. Kinds compose freely; an explicit root may pair with a same-kind library root under §5.2. Reject larger receipts server-side.
+**Selection cardinality**: The default page permits one registered root per kind plus one explicit root; its explicit root may pair with a same-kind library root under §5.2. Quick has no page or catalog selection and accepts at most one supplied exact root per declared kind (four roots total). Kinds compose freely in both profiles. Reject larger default receipts server-side; require an oversized or duplicate-kind Quick input to converge in chat before installation, never through Confirm UI.
**Hard rule — raw source boundary**: A raw PPTX is not a Step 3 workspace. Raw PPTX plus new content uses [`template-fill-pptx`](../template-fill-pptx.md). When the user wants reusable SVG/template generation, run [`create-template`](../create-template.md) first and return with its validated workspace root. Never add Master/Layout/placeholder structure directly to an existing PPTX or SVG project.
@@ -78,9 +83,9 @@ Before copying a Deck or Layout workspace, inspect every SVG root and slot. Bran
| Kind | Install behavior |
|---|---|
| `brand` | Install `templates/` plus existing `images/` and `icons/`; ignore `exports/`. Identity is constrained; structure remains free. |
-| `style` | Install `templates/design_spec.md` only. Ignore sibling project scaffolding and reject a library Style carrying asset/review payloads. Expose reusable direction/method without identity truth, page prototypes, or native structure. Style-only and Style + Brand derive `template_reuse_scope: style` and stay flat; Style + Layout/Deck follows the selected structure plan. A Style workspace never activates visual review. |
-| `layout` | Install the same portable roots. Expose the actual reusable structure; Strategist later inspects the prototypes and derives the application plan automatically. |
-| `deck` | Install the same portable roots. Expose descriptive application context, identity, structure, and the actual prototype roster; Strategist compares them with the current communication contract and content, then derives the application plan automatically. |
+| `style` | Install `templates/design_spec.md` only. Ignore sibling project scaffolding and reject a library Style carrying asset/review payloads. Expose reusable direction/method without identity truth, page prototypes, or native structure. Default Style-only and Style + Brand derive `template_reuse_scope: style` and stay flat; Style + Layout/Deck follows the selected structure plan. Quick always realizes the resolved combination as flat pages. A Style workspace never activates visual review. |
+| `layout` | Install the same portable roots. Expose the actual reusable structure; Default Strategist later inspects the prototypes, while Quick's current agent uses them to derive its transient flat authoring plan. |
+| `deck` | Install the same portable roots. Expose descriptive application context, identity, structure, and the actual prototype roster; Default Strategist or Quick's current agent compares them with the current communication contract and content, then derives the applicable plan. |
For a compatible legacy-flat package, route SVG/spec/non-bitmaps to project `templates/`, bitmaps to project `images/`, and declared icons to project `icons/`. Do not infer legacy Master/Layout semantics from the flat directory shape.
@@ -94,45 +99,47 @@ For a compatible legacy-flat package, route SVG/spec/non-bitmaps to project `tem
If the normalized source root equals the target project root, consume it in place and copy nothing. An in-place workspace cannot participate in multi-path fusion. Ignore source `exports/`; it contains review artifacts, not portable template inputs. Empty optional roots remain absent.
**Hard rule — project-local consumer boundary**: After installation/fusion,
-template-aware Strategist work from Stage 2 onward and every later role read
-only `<project_path>/templates/` and the project-local `images/` / `icons/`
-pools. The original library or external root
+Default template-aware Strategist work from Stage 2 onward, Quick's current
+agent before direct authoring, and every later role read only
+`<project_path>/templates/` and the project-local `images/` / `icons/` pools. The original library or external root
is installation input, not a later prompt source. If source and target are the
same project root, that in-place root already satisfies this boundary.
Template SVGs are authoring prototypes, not export-time overlays. The generated page remains complete in `svg_output/`; `page_layouts` selects the complete prototype and its explicit structure contract for authoring.
+Quick instead realizes the selected prototypes into complete flat, Slide-local
+SVGs and never writes `page_layouts` or Master/Layout/placeholder metadata.
## 5. Fuse Multiple Workspace Paths
-Fuse different kinds or at most two same-kind roots. Resolve template segment/asset conflicts before writing. Never read, predict, or revise Stage 1 here.
+Fuse different kinds or, in Default only, at most two same-kind roots. Resolve template segment/asset conflicts before writing. Never read, predict, or revise Stage 1 here. Default obtains required conflict decisions through its active confirmation surface. Quick follows explicit conflict instructions; an unresolved material compatibility conflict is a hard prerequisite handled in chat, never by launching Confirm UI or by using path order.
### 5.1 Different Kinds
-Resolve four whole template segments. This table selects the installed starting owner; current user instructions and later confirmation still govern project use:
+Resolve four whole template segments. This table selects the installed starting owner; current user instructions and the caller's later consuming plan still govern project use:
| Segment | Starting owner |
|---|---|
-| Identity | Brand, otherwise Deck, otherwise unresolved until Stage 2. Style color/type/icon/image values are direction candidates, never identity truth. |
-| Structure | A compatible Layout, otherwise Deck, otherwise unresolved/free design until Stage 2. Style owns no canvas, prototype, Master/Layout, slot, or page mapping. |
-| Reusable application context | Deck only when present. Preserve it for the later Stage-2 comparison; it never becomes the current project's application contract. |
-| Direction / method | Style when present, otherwise unresolved until Stage 2. Actual Deck prototypes and Signature facts may inform compatibility, but Deck does not own the Style-only method segment. |
+| Identity | Brand, otherwise Deck, otherwise unresolved until the consuming plan (Default Stage 2 or Quick active context). Style color/type/icon/image values are direction candidates, never identity truth. |
+| Structure | A compatible Layout, otherwise Deck, otherwise unresolved/free design until the consuming plan. Style owns no canvas, prototype, Master/Layout, slot, or page mapping. |
+| Reusable application context | Deck only when present. Preserve it for the consuming comparison; it never becomes the current project's application contract. |
+| Direction / method | Style when present, otherwise unresolved until the consuming plan. Actual Deck prototypes and Signature facts may inform compatibility, but Deck does not own the Style-only method segment. |
Replace each selected segment wholesale; do not mix its fields implicitly. Brand or Deck identity replaces any identity-adjacent defaults carried by Style. A Style direction may adapt to that resolved identity, but cannot relabel its candidates as official brand facts.
-Before Layout overrides Deck structure, compare Deck's reusable roles with Layout roles, slots, and capacity. On mismatch, offer exactly three remedies: retain Deck structure, select another Layout, or omit Deck. Do not invent the current project contract before Stage 1.
+Before Layout overrides Deck structure, compare Deck's reusable roles with Layout roles, slots, and capacity. On mismatch, offer exactly three remedies: retain Deck structure, select another Layout, or omit Deck. Default must not invent the current project contract before Stage 1; Quick compares against the current request/content and treats any unresolved material mismatch as a chat hard prerequisite.
-Before Style overlays Deck guidance, verify that its method serves Deck's reusable context and fits the selected structure. On mismatch, require omitting Style or choosing a compatible Style/structure; never silently weaken a segment. Stage 2 separately checks the result against the confirmed project contract.
+Before Style overlays Deck guidance, verify that its method serves Deck's reusable context and fits the selected structure. On mismatch, require omitting Style or choosing a compatible Style/structure; never silently weaken a segment. Default Stage 2 separately checks the result against the confirmed project contract; Quick checks it against the current request/content before authoring.
-Field-level micro-adjustments such as a primary-color override are not Step 3 fusion. Carry them into the normal Strategist confirmation fields.
+Field-level micro-adjustments such as a primary-color override are not workspace fusion. Default carries them into the normal Strategist confirmation fields; Quick treats explicit adjustments as direct transient authoring constraints.
### 5.2 Same Kind
-Do not use path order as priority. Report every segment-level difference and ask the user to choose workspace A, workspace B, or select per segment. Only the per-segment choice opens a segment-by-segment resolution. Two Style workspaces conflict over the complete Direction / method segment. Do not resolve field-level conflicts here. Three or more same-kind paths require the user to converge to at most two.
+Default only: do not use path order as priority. Report every segment-level difference and ask the user to choose workspace A, workspace B, or select per segment. Only the per-segment choice opens a segment-by-segment resolution. Two Style workspaces conflict over the complete Direction / method segment. Do not resolve field-level conflicts here. Three or more same-kind paths require the user to converge to at most two. Quick accepts one root per kind and therefore never enters this subsection.
### 5.3 Fused Provenance
-Write one final `<project>/templates/design_spec.md`. Immediately under its H1, record every source kind/path, base or override role, and user-resolved segment conflict:
+Write one final `<project>/templates/design_spec.md`. Immediately under its H1, record every source kind/path, base or override role, and resolved segment conflict with its explicit authority:
```markdown
> **Fused from:**
@@ -153,4 +160,4 @@ Single-path installs do not add provenance. Set fused frontmatter `kind` from th
- [x] Every kind schema passed preflight; structured SVG checks ran only for Layout/Deck inputs
- [x] All collisions and fusion conflicts were resolved before one atomic install
- [x] `<project_path>/templates/` and any portable sibling assets are complete and are the only downstream template source
-- [ ] **Next**: Return to [`generate-pptx.md`](../generate-pptx.md) Step 4
+- [ ] **Next**: Default returns to [`generate-pptx.md`](../generate-pptx.md) Step 4; Quick returns to [`quick-generate`](../profiles/quick-generate.md) §2