Skill: DRR Dependency Analysis (Credit Scope) — Leg1 Spread Ticket Generator

Extract CDM field paths from Rosetta DSL rules into a Jira-ready dependency map.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zentai/bayes_excersice --skill skill-drr-dependency-analysis-credit-scope-leg1-spread-ticket-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill: DRR Dependency Analysis (Credit Scope) — Leg1 Spread Ticket Generator
Source: https://github.com/zentai/bayes_excersice/tree/main
Command: npx skills add https://github.com/zentai/bayes_excersice --skill skill-drr-dependency-analysis-credit-scope-leg1-spread-ticket-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the extraction and mapping of data dependencies for DRR rules, turning Rosetta DSL rule definitions into a structured dependency map suitable for governance and auditing.

Core Features & Use Cases

  • Dependency extraction: identifies CDM model paths referenced by a Rosetta DSL rule and its sub-functions.
  • Alias expansion: expands aliases to full CDM paths for developer clarity.
  • Output structure: produces a Jira-friendly Dependency Map with direct/conditional paths, function usage context, and canonical CDM paths.
  • Use Case: Regulatory reporting analysis, risk governance, and documentation of rule impacts.

Quick Start

Run the DRR dependency analysis by supplying a Rosetta DSL snippet and the rule name to generate a Jira-ready Leg1 spread ticket.

Frequently Asked Questions about Skill: DRR Dependency Analysis (Credit Scope) — Leg1 Spread Ticket Generator

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

FAQPage Schema
How do I extract CDM data dependencies from a Rosetta DSL rule for DRR governance?

Generate a Jira-ready dependency map from a Rosetta DSL rule by supplying the rule snippet and rule name. The analysis identifies all referenced CDM field paths, expands aliases to full canonical paths, and structures the output with function usage context including file and line details.

What is alias expansion for CDM paths in regulatory reporting analysis?

Generate a Jira-ready dependency map from a Rosetta DSL rule by supplying the rule snippet and rule name. The analysis identifies all referenced CDM field paths, expands aliases to full canonical paths, and structures the output with function usage context including file and line details.

Can I automate Jira ticket creation for DRR dependency mapping?

Generate a Jira-ready dependency map from a Rosetta DSL rule by supplying the rule snippet and rule name. The analysis identifies all referenced CDM field paths, expands aliases to full canonical paths, and structures the output with function usage context including file and line details.

Does dependency analysis capture conditional CDM field path usages?

Generate a Jira-ready dependency map from a Rosetta DSL rule by supplying the rule snippet and rule name. The analysis identifies all referenced CDM field paths, expands aliases to full canonical paths, and structures the output with function usage context including file and line details.

How do I document rule impacts for DRR compliance using Rosetta DSL?

Generate a Jira-ready dependency map from a Rosetta DSL rule by supplying the rule snippet and rule name. The analysis identifies all referenced CDM field paths, expands aliases to full canonical paths, and structures the output with function usage context including file and line details.