mr-roam-node

Translates JIRA tickets into standardized org-roam nodes with GIVEN/WHEN/THEN acceptance criteria.

Updated May 3, 2024
One-click install
npx skills add https://github.com/Kyonax/dot-files --skill mr-roam-node
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mr-roam-node
Source: https://github.com/Kyonax/dot-files/tree/main/.config/doom-mac/gptel-directives/skills/mr-roam-node
Command: npx skills add https://github.com/Kyonax/dot-files --skill mr-roam-node

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mr-roam-node

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

FAQPage Schema
How do I automate syncing JIRA tickets to org-roam nodes?

To automate JIRA-to-org-roam sync, you need a tool that translates JIRA ticket descriptions into standardized org-roam nodes, normalizing acceptance criteria into GIVEN/WHEN/THEN structure and maintaining a synced sprint board index.

How do I normalize JIRA acceptance criteria into GIVEN/WHEN/THEN format for org-mode?

You normalize JIRA acceptance criteria into GIVEN/WHEN/THEN format by processing 6 distinct JIRA description variants and enforcing org-mode syntax compliance to generate standardized org-roam nodes.

Can I validate git diffs against JIRA acceptance criteria automatically?

Yes, validating git diffs against JIRA acceptance criteria is possible by cross-referencing the diff with node acceptance criteria, event tracking specs, and QA instructions to generate structured pass/fail validation reports.

Does this JIRA to org-roam translation work with different JIRA description formats?

Yes, the JIRA to org-roam translation supports 6 distinct JIRA description format variants, normalizing them into structured metadata headers and section layouts to prevent loss of validation-critical ticket data.

How do I keep my org-roam sprint board index synced with JIRA status?

To keep an org-roam sprint board index synced with JIRA status, automate sprint board lane updates, issue links, and statistics cookie recalculation across a BACKLOG and Sprint Board dashboard.