generate-slides
Scannednpx machina-cli add skill arudita-zzz/app-dev-prompt-suite/generate-slides --openclawGenerate Marp presentation slides from enterprise-dev-suite phase artifacts.
Steps
0. Initialization
- Read conventions for defaults
1. Resolve Source Directory
- Parse
-s <path>from arguments - If not specified: AskUserQuestion for task name / Type Anything
- Set source dir:
.claude/claudeRes/docs/{task_name} - If dir not found: AskUserQuestion for manual path / Type Anything
2. Detect Phases
- Parse
-pfrom arguments (values:all,feasibility,design,implementation; comma-separated for multiple) - If not specified: auto-detect by checking existence of:
feasibility_report.md→ feasibilitysolution_design.md→ designimplementation_report.md→ implementation
- AskUserQuestion: confirm detected phases / select manually / Type Anything
3. Check Output Format
- Parse
-ffrom arguments (default:md) - If format is not
md: check Marp CLI availability- Run:
which marp || which npx - If neither found: warn user, offer install guidance, fallback to
md
- Run:
4. Extract Content
Read content-extraction instructions and execute. For each selected phase: read summary + detail artifacts per slide-format.md.
5. Build Slides
Assemble Marp markdown per slide-format.md:
- Frontmatter: theme=default, paginate=true, footer="Generated by enterprise-dev-suite"
- Include only sections for selected phases
- Adapt all headings and content to the document language (see conventions.md)
- Preserve Mermaid code blocks verbatim
- Max 12 content lines per slide; if exceeded, delegate to document-summarizer agent
6. Write Output
- Determine task_name from source directory name
- Save to:
.claude/claudeRes/docs/{task_name}/slides_{task_name}.md
7. Convert (conditional)
- If format ≠
md: executescript/convert-slides.sh <input.md> <format> - Report conversion result or error
8. Done
- Display output file path(s)
- AskUserQuestion: open preview / regenerate with different options / done / Type Anything
Constraints
- Docs dir:
.claude/claudeRes/docs - Document language: see conventions
- Mermaid blocks must never be summarized or modified
Source
git clone https://github.com/arudita-zzz/app-dev-prompt-suite/blob/main/plugins/enterprise-dev-suite/skills/generate-slides/SKILL.mdView on GitHub Overview
Generates Marp presentation slides from enterprise-dev-suite phase artifacts for technical review. It reads feasibility, design, and implementation content, assembles a slide deck with standardized frontmatter, and saves the output under the .claude/claudeRes/docs/{task_name}/slides_{task_name}.md. Optional conversion to other formats can be performed if requested.
How This Skill Works
The tool resolves the source directory from -s (prompting if missing), auto-detects or confirms phases via artifacts, then reads content using content-extraction rules to assemble Per-Phase slides per slide-format.md. It builds a Marp markdown file with frontmatter (theme, paginate, footer), preserves Mermaid blocks verbatim, enforces a 12-line content limit per slide, saves to .claude/claudeRes/docs/{task_name}/slides_{task_name}.md, and can convert to md/pptx/pdf/html if a format other than md is requested.
When to Use It
- You need a technical-review deck created from phase artifacts (feasibility, design, implementation).
- You want a consistent slide template across multiple tasks with standard Marp frontmatter.
- You must output in markdown first, then optionally convert to pptx/pdf/html later.
- Artifacts live under .claude/claudeRes/docs and you want a single slides_<task>.md file per task.
- You need to regenerate slides after updating phase artifacts or task naming.
Quick Start
- Step 1: Run with -s <source_dir> and -p <phases> (e.g., all) and -f <md|pptx|pdf|html> as needed.
- Step 2: The agent reads artifacts, extracts content, and builds slides_<task>.md under .claude/claudeRes/docs/{task_name}/.
- Step 3: Open the generated slides file or run the conversion script if you need a non-md format.
Best Practices
- Verify the source directory (-s) and the task name before running.
- Review detected phases (-p) and adjust manually if needed.
- Keep Mermaid blocks intact; they must be preserved verbatim.
- Limit slide content to 12 lines; delegate excess content to a summarizer if required.
- Use slides_{task_name}.md as the canonical artifact for reviews and sharing.
Example Use Cases
- Feasibility + Solution Design deck for a project kickoff technical review.
- Implementation readiness slides prepared for internal due diligence.
- Cross-phase status deck for weekly stakeholder updates.
- Marp slides exported to HTML for lightweight web sharing with teams.
- Executive summary deck generated from phase artifacts for leadership review.
