interaction-map

Transform user scenarios into structured visual interaction maps across platforms.

4|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/CaufieldZ/pm-workspace-public --skill interaction-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interaction-map
Source: https://github.com/CaufieldZ/pm-workspace-public/tree/main/.claude/skills/interaction-map
Command: npx skills add https://github.com/CaufieldZ/pm-workspace-public --skill interaction-map

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill converts scattered requirements and scene lists into a cohesive, visual interaction map (IMAP) that guides design, development, and QA across devices and endpoints.

Core Features & Use Cases

  • Skeleton generation creates a structured scaffold (PARTs, Scenes) with device-specific mockups for quick validation.
  • Stepwise content filling supports the end-to-end workflow: Step A skeleton creation, Step B filling Scenes, Step C self-check, and Step D incremental patching to deliver consistent visuals.
  • Validation and reuse ensure cross-end alignment and maintainability for future iterations across PM workflows.

Quick Start

Generate the skeleton from your context and scene-list, then fill scenes in batches and run the self-check before delivery.

Frequently Asked Questions about interaction-map

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

FAQPage Schema
How do I turn user flows into a visual interaction map for PM workflows?

Transform user scenarios into a visual interaction map by generating a structured scaffold of parts and scenes, then batch-filling content and running self-checks to align product, design, and engineering.

What is the stepwise process to create an interaction map from scattered requirements?

The stepwise interaction map production involves creating a skeleton scaffold, filling scenes with content in batches, running self-checks for validation, and applying incremental patches to maintain visual consistency.

Can I generate device-specific mockups for cross-platform user flows?

Yes, skeleton generation creates device-specific mockups within the interaction map, ensuring cross-platform alignment for design, development, and QA across different endpoints.

Does the interaction map workflow support incremental updates without breaking existing scenes?

Yes, regression-safe patching allows incremental updates to the interaction map, ensuring consistent visuals and maintainability for future iterations without disrupting existing scenes.

What's the best way to validate cross-end alignment in user scenario documentation?

Run the built-in self-check after batch-filling scenes to validate cross-end alignment and ensure the interaction map maintains consistency across all platforms and endpoints.