菜单
Deck Master planning entry for context intake, brief, claim map, narrative plan, page tasks, and sourcing intent inside a Deck Master run. Use when the user asks to plan a solution deck structure, turn customer material into a narrative plan, or prepare page-level production tasks.
用 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-planner |
| description | Deck Master planning entry for context intake, brief, claim map, narrative plan, page tasks, and sourcing intent inside a Deck Master run. Use when the user asks to plan a solution deck structure, turn customer material into a narrative plan, or prepare page-level production tasks. |
| triggers | ["plan a solution deck","build deck brief","make a claim map","create a narrative plan","prepare page tasks"] |
Use this skill for planning work inside Deck Master.
Start with Deck Master readiness:
~/.deck-master/bin/deck-master setup-status --include-suite --output json
If setup, workspace, or required suite readiness is blocked, return to the Deck Master setup ceremony before creating production artifacts. Explain the missing readiness in normal language, confirm the intended workspace when needed, run safe setup or repair commands, and verify status again.
Deck Master run state owns production planning. Do not create final narrative plans, page tasks, or sourcing decisions outside a Deck Master run.
~/.deck-master/bin/deck-master start --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master build-brief --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master build-claim-map --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master autoplan --run-dir <run_dir> --run-id <run_id> --planning-mode narrative_v2
~/.deck-master/bin/deck-master search-library --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master decide-sourcing --run-dir <run_dir> --run-id <run_id>
Planning output must be visible through Deck Master artifacts such as
deck_brief.json, claim_map.json, narrative_plan.json,
page_tasks.json, and sourcing_plan.json.
Planning workflow for claim map, narrative plan, page tasks, and sourcing intent.
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-planner. Stage completion is validated by the contract entry/exit validator and handoff/approval runtime, not by command return code.
deck-master autoplan --run-dir <run_dir>
deck-master workflow status --run-dir <run_dir>
deck-master run-state --run-dir <run_dir>
narrative_plan, page_tasks, sourcing_intent
deck-sourcing
Keep internal-only production notes out of customer-visible content. Never bypass the final client export approval. Obey the stage contract's transition policy.