What problem does it solve? Manually transcribing story maps and backlog documents into Elements.cloud is repetitive and error-prone. This Skill automates the creation of Requirements and Stories through the Elements REST API, keeping parent-child links intact. ## Core Features & Use Cases - Requirement Creation: Push Epics as Requirements with priority, impact, risk, tags, release, and assignee fields via POST /requirements. - Story Creation with Linking: Create Stories with acceptance criteria and external IDs, linked to parent Requirements by ID. - Field Mapping Guidance: Built-in mapping table converts story map fields (Epic title, US IDs, P1/P2/P3 priorities) into Elements API fields. - Use Case: A business analyst finishes a story map workshop and pushes 5 Epics as Requirements and 20 user stories as linked Stories into their Elements Space in one session, with per-item success reporting. ## Quick Start Push the story map in this document to Elements.cloud, creating one Requirement per Epic and linking each user story to its parent Requirement.