radar-compliance

Compare ITSAC Markdown technologies against Technology Radar Word statuses and generate a compliance report.

Updated Aug 23, 2026

Search Tags:#technology #compliance #reporting #analyze #radar #ITSAC

Ready to run

npx skills add https://github.com/ukrsite/kiro-workflows --skill radar-compliance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: radar-compliance
Source: https://github.com/ukrsite/kiro-workflows/tree/main/skills/shared-skills/radar-compliance
Command: npx skills add https://github.com/ukrsite/kiro-workflows --skill radar-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technologies documented in ITSAC files often need alignment with the Technology Radar to ensure governance and strategy are in sync. This Skill automates the validation of that alignment, surfacing gaps and confirming compliant technology choices.

Core Features & Use Cases

Extract ITSAC technologies: Read the ITSAC Markdown file and collect the list of technologies mentioned.
Extract Radar statuses: Read the Technology Radar Word document to capture technology names and their radar statuses (Adopt, Trial, Assess, Hold).
Compare and report: Map ITSAC technologies to radar entries and generate a comprehensive compliance report with statuses and recommendations.
Use Case: Use this in quarterly architecture reviews to verify that new technologies in ITSAC are appropriately positioned in the radar before approval.

Quick Start

Provide the ITSAC Markdown file path and the Technology Radar Word document path, then run the skill to generate radar_compliance_report.md.

Frequently Asked Questions about radar-compliance

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

FAQPage Schema

How do I validate ITSAC technologies against a Technology Radar?▼

To validate ITSAC technologies against a Technology Radar, you need to parse an ITSAC Markdown file and a Technology Radar Word document to map technologies to radar statuses and generate a structured compliance report.

What is the process for mapping ITSAC inventory to radar statuses?▼

Mapping an ITSAC inventory to radar statuses involves extracting technologies from a Markdown file, comparing them against Adopt, Trial, Assess, or Hold entries in a Word document, and outputting a compliance report with alignment recommendations.

Can I compare technologies across Markdown and Word documents for architecture reviews?▼

Yes, you can compare technologies across Markdown and Word documents for architecture reviews by applying deterministic parsing logic to extract and reconcile inventory items with radar statuses to assess project portfolio adoption readiness.

How do I generate a radar compliance report for project portfolios?▼

You generate a radar compliance report by providing an ITSAC Markdown file path and a Technology Radar Word document path, which allows the workflow to cross-format parse, compare, and output a structured Markdown compliance file.

When do I need to check ITSAC files for Technology Radar alignment?▼

You need to check ITSAC files for Technology Radar alignment during quarterly architecture reviews to verify new technologies are appropriately positioned in the radar and satisfy governance and policy requirements before project approval.