figjam-extract-user-stories

Extract visible ADO User Story components from FigJam boards into a markdown table.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/klemensms/mcp-consultant-tools --skill figjam-extract-user-stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figjam-extract-user-stories
Source: https://github.com/klemensms/mcp-consultant-tools/tree/main/.claude/skills/figjam-extract-user-stories
Command: npx skills add https://github.com/klemensms/mcp-consultant-tools --skill figjam-extract-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract ADO User Story components from FigJam boards and output them as a structured markdown table. Use when users ask to extract user stories from FigJam, analyze FigJam for ADO items, get ADO work items from FigJam boards, or any request involving extracting structured ADO/user story data from Figma/FigJam boards. Handles nested components, parent context extraction, and link generation.

Core Features & Use Cases

  • Identify visible ADO User Story Components (standalone or nested) within FigJam boards.
  • Extract relevant properties from componentProperties and, when nested, from parent components to populate Context.
  • Produce a clean markdown table with ADO and FigJam links, including handling of nested contexts.

Quick Start

Run this skill on a FigJam board containing ADO User Story Components to generate the markdown table.

Frequently Asked Questions about figjam-extract-user-stories

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

FAQPage Schema
How do I extract Azure DevOps user stories from a FigJam board?

To extract ADO user stories from FigJam, identify all visible ADO User Story Components, parse their componentProperties and node structures, and compile the extracted data into a structured markdown table with ADO and FigJam links.

Can I get context for nested ADO work items in a FigJam board extraction?

Yes, when extracting nested ADO user story components from FigJam, the process derives context from parent components by parsing their node structures, ensuring the extracted markdown table accurately reflects the hierarchical relationship of the work items.

Does the FigJam ADO user story extraction include non-visible items?

No, the extraction specifically parses componentProperties and node structures to identify and avoid non-visible items on the FigJam board, ensuring the resulting markdown table only contains visible ADO User Story Components.

What is the best way to convert FigJam components into a markdown table?

The best way to convert FigJam components into a markdown table is to parse componentProperties of visible ADO User Story Components, extract parent context for nested items, and compile the properties and links into a structured markdown format.