What problem does it solve?
Manually creating and maintaining org-roam nodes from JIRA tickets is time-consuming, error-prone, and often leads to lost validation-critical data like acceptance criteria, event tracking tables, and design links. Keeping the sprint board index in sync with JIRA status and issue links adds further overhead, leading to outdated workflow dashboards.
Core Features & Use Cases
- Standardized Node Generation: Automatically creates consistent org-roam nodes for JIRA stories, tasks, and bugs, normalizing 6 different JIRA description formats into structured GIVEN/WHEN/THEN acceptance criteria, metadata headers, and section layouts.
- Two-Layer Index Management: Maintains a BACKLOG (source of truth) and Sprint Board (workflow view) dashboard that auto-syncs with JIRA ticket status, issue links, and resolution state, with automatic statistics cookie recalculation.
- Development Validation: Cross-references git diffs against node acceptance criteria, event tracking specs, and QA instructions to generate structured pass/fail validation reports for development work.
- Use Case: For Madison Reed development teams, this skill eliminates manual ticket documentation, ensures no validation-relevant data is lost during JIRA-to-org translation, and automates sprint board maintenance.
Quick Start
Ask the mr-roam-node skill to generate an org-roam node for JIRA ticket DOTCOMPB-7289 and sync the sprint board index with its current status.