Slider Plan (Orchestrator)

Goal

Produce a plan only (no file edits, no rendering) that routes the user request to the right v2 skill(s):

• content-prompts → material → $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md
• styled-prompts → content prompt + style brief → $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md
• styled-artifacts → styled prompt → images + $HUMAN_MATERIAL_PATH/slides/<deck>/artifacts/<deck>/<deck>.pdf / image-PPTX $HUMAN_MATERIAL_PATH/slides/<deck>/artifacts/<deck>/<deck>.pptx

The plan must be written in the same format as the create-plan skill template.

Routing

Decide the starting point from the user’s input:

• Raw notes / folder / “material” → run content-prompts
• Already has $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md → start at styled-prompts
• Already has $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md → start at styled-artifacts

Decide the stopping point from the requested output:

• Wants Content PROMPT → stop after content-prompts
• Wants Styled PROMPT → stop after styled-prompts
• Wants PDF / images / image-PPTX → include styled-artifacts
• Wants editable PPTX → out of scope for this repo (the upstream pptx skill was proprietary)

Style selection (v2)

• If the user names a style, use $HUMAN_MATERIAL_PATH/slides/styles/<style>.md.
• Otherwise, use $HUMAN_MATERIAL_PATH/slides/<deck>/configs/deck.yaml (style:) if present.
• If neither is available, default to $HUMAN_MATERIAL_PATH/slides/styles/blueprint.md (or ask 1 question if the choice matters).

Review policy (required)

Keep generation cheap:

• Review happens on prompts (prompts/content/* and/or prompts/styled/*).
• Do not plan “regenerate + review” loops for final artifacts.

Output format

Output only a plan, using the exact template structure:

• # Plan
• ## Scope
• ## Action items (include the exact skill invocations and file paths)
• ## Open questions (max 3; ask only if blocking)

References

• Routing cheatsheet: references/routing.md
• Example plans: references/examples.md

Completion behavior (required)

When this skill is triggered:

1. Do only this step: output a plan (no file edits, no rendering).
2. The plan must include the exact next skill invocations and any CLI commands needed.
3. Do not execute the plan steps automatically.