Create Strategy Consulting PPTX

Create Strategy Consulting PPTX

Convert source material into decision-ready slides whose logic, not decoration, carries the message.

Handle the initial interaction

• If invoked without source material, reply only: 準備できました。スライド化したい資料または対象セクションを送ってください。
• If a long PDF or report is provided without a target, ask which pages or section to convert. Do not select the scope silently.
• Default to one slide for one source section per request unless the user asks for a deck or the content clearly requires pagination.
• Let the user provide raw, unstructured material; perform the structuring yourself.

Load the detailed standard

Read references/slide-standard.md before analyzing or producing a slide. Apply its design tokens, native-PowerPoint requirements, and final checks.

Execute the workflow

1. Establish source boundaries

• Record the source name, section, page, reporting date, and units when available.
• Preserve qualifiers, exclusions, non-exhaustive statements, and the time basis.
• Distinguish every material statement internally as:
  • fact: explicit in the source
  • synthesis: an analytical grouping or summary of facts
  • implication: a reasonable decision-relevant consequence
  • unknown: unsupported by the input
• Never create missing values, probabilities, priorities, chronology, actors, steps, or causal relationships.
• Label analytical classifications or hypotheses when a reader could mistake them for source facts.

2. Form the governing message

• Identify the single most important conclusion for the page.
• Write a short topic title, usually a noun phrase.
• Write a one- or two-line lead that states the key conclusion or implication and includes decisive evidence where useful.
• Make the body prove or explain the lead.
• Do not add a routine bottom-of-slide “So What” strip; integrate the implication into the lead.

Create a compact claim ledger before layout. For every displayed number, delta, date, and directional statement, record the exact display text, its source passage, and its fact/synthesis/implication classification. Use this ledger during final verification.

3. Structure the evidence

Before drawing, separate the input into relevant units:

• facts and metrics
• supporting evidence
• causes and background
• mechanisms
• outcomes and impact
• actions
• conditions, exceptions, and exclusions
• implications
• unknowns

Retain useful explanatory detail. Do not compress causes, conditions, examples, or exceptions into context-free labels merely to make the page look sparse.

4. Select the visual logic

Compare two or three materially different structures internally. Consider a table or matrix, process, swimlane, causal chain, driver tree, before/after, architecture, roadmap, learning loop, waterfall, risk landscape, convergence structure, ecosystem, or a composite chart-and-explanation layout.

Select the structure that best preserves the source relationships, supports a decision, remains readable at high density, stays editable, and minimizes invented relationships.

Guardrails:

• Do not use a flow without explicit sequence.
• Do not use a causal diagram without supported causality.
• Do not use a risk heatmap without likelihood and impact data.
• Do not force unrelated information into a shared table.
• Do not reduce related information to a wall of independent cards.
• Combine a primary and supporting structure when one visual cannot explain both “why” and “so what.”

5. Select the layout

Compare three genuinely different arrangements internally, such as:

• full-width primary visual with direct annotation
• top/bottom evidence and interpretation
• small multiples
• central visual with surrounding explanation
• timeline with execution lanes
• primary visual plus a compact supporting region

Choose based on visual space, natural reading order, proximity of evidence and explanation, balanced density, visible relationships, and editability. Do not expose candidate scores or chain-of-thought.

6. Build the PowerPoint

• Produce a 16:9 editable .pptx whenever the environment supports PowerPoint generation.
• Use native PowerPoint text, shapes, tables, charts, lines, arrows, and connectors.
• Put text directly inside its containing shape; do not overlay a separate text box on a shape.
• Prefer native tables or individually meaningful shapes over a background rectangle with text boxes layered on top.
• Use unfilled, unlined rectangles for standalone text.
• Keep meaningful units independently movable and editable.
• Express increase and decrease with explicit words such as 前年比8%増 and 前年比12%減. Use ▲, ▼, or arrow glyphs only when the source uses them and their meaning is unambiguous to the intended audience.
• If direct PPTX generation is unavailable, provide a sufficiently precise slide specification for later native implementation; do not present a flattened image as the final deliverable.
• For multiple slides, keep the title, lead, body, footer rule, source, page number, and bottom-right label in fixed positions.

7. Validate and revise

• Reopen or parse the generated file and verify it is structurally valid.
• Run python3 <skill-directory>/scripts/validate_pptx.py <output.pptx> --strict. Fix every error and review every warning; leave a warning unresolved only when it reflects an intentional, source-supported exception.
• Render slides to images when tooling permits and inspect for overflow, overlap, clipping, awkward line breaks, collisions, imbalance, and unintended style drift. Treat a custom preview as valid only if it renders every shape type used on the slide, including tables and charts.
• Treat the validator as a structural gate, not a substitute for visual inspection.
• Confirm that the title identifies the topic, the lead contains the conclusion, and the body substantiates it.
• Verify every item in the claim ledger against the source, including sign, direction, unit, period, and scope.
• Confirm all major elements remain editable.
• Fix structural or layout problems at their source; do not hide them with smaller type or decorative patches.

Report completion

Keep the handoff concise. State:

• the structure selected
• the file created
• the validation performed

Do not provide a long production diary unless requested.