Skip to content

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

docs(planning): complete Design Spec projection gates

hugohe3c70f57a4aafe
diff --git a/skills/ppt-master/templates/spec_lock_reference.md b/skills/ppt-master/templates/spec_lock_reference.md
index 043d608a..1724f731 100644
--- a/skills/ppt-master/templates/spec_lock_reference.md
+++ b/skills/ppt-master/templates/spec_lock_reference.md
@@ -1,10 +1,10 @@
# Execution Lock Structure
-`spec_lock.md` is a compact Markdown data contract. Its machine contract is [`schemas/spec_lock.schema.json`](./schemas/spec_lock.schema.json); authoring starts from [`scaffolds/spec_lock.md`](./scaffolds/spec_lock.md).
+`spec_lock.md` is the machine projection of an audited `design_spec.md`. After confirmation fidelity passes, start from [`scaffolds/spec_lock.md`](./scaffolds/spec_lock.md); [`schemas/spec_lock.schema.json`](./schemas/spec_lock.schema.json) owns its grammar.
## 1. Create the artifact
-Run the scaffold command once, then fill or remove placeholder data lines:
+After Generate Step 4 Gate 1, run once and project values from the Design Spec:
```bash
python3 skills/ppt-master/scripts/project_manager.py scaffold-lock <project_path>
@@ -88,6 +88,6 @@ Structured section value shapes:
python3 skills/ppt-master/scripts/project_manager.py validate <project_path>
```
-Validation reads the existing Markdown form. It reports unresolved `[fill...]` scaffold placeholders, wrong section or field casing, unknown sections or fields, illegal declared enums, malformed page keys, catalog keys without their corresponding SVG asset, broken structured-layout references, and unmet required / forbidden conditional sections. It does not rewrite the lock and is not an automatic generation gate.
+Validation reports unresolved `[fill...]` placeholders, wrong casing, unknown sections or fields, illegal enums, malformed page keys, missing catalog assets, broken structured-layout references, and unmet conditions. It neither rewrites the lock nor checks semantic projection; Generate Step 4 Gate 2 owns that check.
Field meaning and selection logic stay in the owning Strategist modules. Executor branch references own consumption behavior. The schema owns only artifact grammar and structural conditions.
diff --git a/skills/ppt-master/workflows/generate-pptx.md b/skills/ppt-master/workflows/generate-pptx.md
index 7e49f814..ae9795e0 100644
--- a/skills/ppt-master/workflows/generate-pptx.md
+++ b/skills/ppt-master/workflows/generate-pptx.md
@@ -247,10 +247,11 @@ After filling the lock, compare its machine-relevant values against the complete
## ✅ Strategist Phase Complete
- [x] Read the auto-extracted facts already in `analysis/` (e.g. `source_profile.json`) before the Strategist confirmation stage
- [x] Strategist confirmation stage completed (user confirmed via Confirm UI `result.json` or chat fallback)
-- [x] Final confirmation re-read; `design_spec.md` audited field by field against it with no confirmed value omitted, substituted, or weakened
+- [x] Final confirmation re-read before Design Spec authoring
- [x] Split-mode note appended below the confirmation fields (heavy or normal variant)
- [x] Spec-refinement opt-in line appended (default OFF; only the user's explicit request enters the refine-spec stage)
- [x] Design Specification & Content Outline generated
+- [x] Gate 1 passed: Design Spec preserves every confirmed value
- [x] Execution lock (`spec_lock.md`) projected from the completed Design Spec with no independent design decision
- [x] Communication trace validated: `spec_lock.md ## communication` contains all six contract key lines (optional values may be blank), and every `design_spec.md §IX` Slide block has an `Audience move`
- [ ] **Next**: Auto-proceed to [Image_Generator / Executor] phase