pptx_spec_traceability

Extract PowerPoint specifications into Markdown with traceability IDs written back into the deck.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill pptx-spec-traceability-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pptx_spec_traceability
Source: https://github.com/synthaicode/XRefKit/tree/main/skills/pptx_spec_traceability
Command: npx skills add https://github.com/synthaicode/XRefKit --skill pptx-spec-traceability-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Converting PowerPoint-based specifications into reviewable Markdown often loses the connection to the original slide, object position, and visual context, making omissions hard to verify. This Skill preserves slide-level source pointers and writes traceability IDs back into the deck so reviewers can check coverage directly in the original presentation. ## Core Features & Use Cases - Slide-by-slide extraction: Convert titles, text boxes, tables, images, shapes, callouts, and speaker notes into Markdown fragments with stable traceability IDs. - Visual-to-text linking: Connect images, shapes, and arrows to nearby labels, captions, and notes so visual-only specification items are captured explicitly. - Deck write-back: Write assigned traceability IDs into speaker notes, text boxes, or callouts in the original pptx for direct verification. - Use Case: Given a 40-slide product specification deck, generate Markdown requirement fragments with source pointers, then review the deck itself to confirm no control, step, or label was omitted. ## Quick Start Convert the specification deck at sources/spec.pptx into Markdown fragments with traceability IDs and write the IDs back into the deck.

Frequently Asked Questions about pptx_spec_traceability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a PowerPoint specification into Markdown?▼

Provide the source pptx path, an optional Markdown destination, slide scope, and ID prefix. The Skill reads the deck slide by slide, extracts text boxes, tables, images, and callouts, and produces Markdown fragments with source pointers and traceability IDs.

How are images and shapes in slides captured as specification items?▼

Each visual object is recorded with its slide number and position, then linked to nearby labels, captions, connector arrows, grouped objects, or speaker notes. Visual-only items are extracted explicitly as separate Markdown entries rather than being dropped.

Can traceability IDs be written back into the PowerPoint deck?▼

Yes. Assigned IDs are written into speaker notes, dedicated text boxes, adjacent callouts, comments, or a controlled slide when no safe layout area exists. Extraction is not considered complete until the write-back is verified against the Markdown.

What happens when slide visuals and nearby text disagree?▼

The item is recorded as unknown and both interpretations are kept visible in the unresolved list. The Skill does not force a single reading when the slide layout or visual context is too weak for safe interpretation.

When should I not use PowerPoint-to-Markdown traceability extraction?▼

Avoid it when the deck is not the controlled source of truth or when specifications exist only as prose documents. The workflow assumes a stable source deck under sources/ and meaningful slide structure to anchor source pointers.