القائمة
Deck Master briefing entry for turning raw materials, deep research reports, and meeting notes into customer-visible deck brief inputs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Deck Master workflow autopilot for advancing a run across init, brief, planning, sourcing, production, build, quality, review, and delivery checkpoints.
Deck Master learning entry for delivery outcomes, reusable asset feedback, benchmark results, and workspace learning packs.
Professional Solution Deck Run OS for turning customer context, briefs, historical deck assets, sourcing decisions, product capability handbacks, quality gates, Review Desk state, benchmark runs, and delivery feedback into auditable solution deck workflows. Use when Codex needs to create or resume a Deck Master run, generate a preview from a brief, inspect next steps, run deck quality gates, import narrative advice or review findings, manage PPT Library, PPT Master, PPT Deck Pro Max, or PPT Quality Gate handbacks, export approved page queues, validate benchmark cases, or operate the local Deck Master CLI and Review Desk.
Deck Master sourcing entry for deciding which pages need historical assets, new production, evidence screenshots, or project-specific reference material.
Deck Master build entry for producing delivery-oriented HTML, PDF, PNG, PPTX, artifact manifest, render result, and editability metadata through the PPT Master backend.
Deck Master project workspace initialization entry for creating customer material, reference material, AI process, delivery, quality, and .deck-master metadata directories.
| name | deck-brief |
| description | Deck Master briefing entry for turning raw materials, deep research reports, and meeting notes into customer-visible deck brief inputs. |
| triggers | ["create deck brief","summarize deck materials","turn research into ppt brief","deck brief"] |
Use this skill when the user provides source material and wants Deck Master to extract the business problem, audience, claims, evidence, and deck intent.
~/.deck-master/bin/deck-master import-context-pack --run-dir <run_dir> --input <context_pack.json>
~/.deck-master/bin/deck-master build-brief --run-dir <run_dir>
~/.deck-master/bin/deck-master build-claim-map --run-dir <run_dir>
Keep internal production notes out of customer-visible content. Production notes belong in source metadata, speaker notes, or internal planning fields.
Turn raw material and research into deck brief inputs.
Do not use outside its lane in the Skill OS workflow. Do not treat a successful command return code as stage completion.
Skill OS workflow runtime; stage deck-brief. Stage completion is validated by the contract entry/exit validator and handoff/approval runtime, not by command return code.
deck-master build-brief --run-dir <run_dir>
deck-master workflow status --run-dir <run_dir>
deck-master run-state --run-dir <run_dir>
deck_brief, claim_map_seed
deck-planner
Keep internal-only production notes out of customer-visible content. Never bypass the final client export approval. Obey the stage contract's transition policy.