marp-deck-workflow
Marp Deck Workflow — Presentation Consultant
Purpose
Guide the user through creating a polished MARP deck via 3 consultation rounds (planning, visual design, generation) before each delegation to a sub-skill. This produces higher-quality decks by incorporating user intent at every stage rather than running a silent pipeline.
Inputs
definition/deck-definition.md— optional (created interactively if missing).marp/references/deck-template.md— required (source of truth for style variants)
Outputs
More from raffaelecamanzo/skills
marp-deck-visual-designer
Transform a MARP presentation plan into concrete visual and layout decisions, including generating Mermaid diagrams when explicitly planned. Use only when a deck-plan.md already exists.
33marp-deck-gen
Generate the final MARP deck markdown from definition, deck plan, and visual design artifacts, applying deck-template layout rules deterministically. Use only when all three source artifacts exist.
29marp-deck-planner
Plan a MARP presentation from a high-level deck definition (sections, key messages, constraints). Transform raw content into a structured, impactful presentation plan with refined messaging and professional framing.
27marp-deck-checker
Visual QA on the rendered PDF of a MARP deck. Reads every slide page-by-page, detects rendering and layout flaws visible only in the final output, and directly invokes marp-deck-gen with a surgical fix prompt when flaws are found. No report file is written.
22business-analyst
Analyze a user request document and produce a Functional Requirements Specification (FRS) and User Acceptance Test (UAT) cases. Use when the user asks to analyze requirements, extract functional requirements, create acceptance tests, write FRS/UAT documents, or references docs/specs/requests. Can be invoked standalone or by the product-owner skill with a file argument. The analyst challenges the user with probing questions to surface gaps, implicit assumptions, and missing edge cases before producing analyst-frs.md and analyst-UAT.md at docs/specs/.
7product-owner
Run the full requirements workflow — collaborative scoping, functional analysis (BA), non-functional analysis (technical writer), cross-reference review, and unified SRS generation. Use when the user asks for a "full specification", "SRS", "complete requirements workflow", or "run the product-owner". Orchestrates the business-analyst and technical-writer skills sequentially, then cross-references their outputs to detect conflicts and gaps before producing docs/specs/software-spec.md.
7