architecture-governance_skill

Overview

This skill is an architecture governance expert that evaluates system health across six dimensions and produces prioritized governance tasks and readable reports. It turns metrics into actionable plans, balancing business context with technical risk. Use it to identify technical debt, compare systems, and drive continuous architecture improvements.

How this skill works

The skill ingests system identifiers and metric data, applies a weighted six-dimension evaluation framework, and computes health scores and levels. It generates comparative dashboards, risk-ranked task lists, and templated health reports or periodic governance summaries. Outputs include prioritized remediation tasks with estimated effort and recommended timelines.

When to use it

• After collecting architecture and operational metrics for a single system health check
• When comparing multiple systems to find TOP risks and prioritize governance effort
• To generate a governance plan or sprint-sized remediation tasks from an issue list
• When preparing regular governance communications such as weekly or monthly reports
• During architecture review meetings to ground discussions in objective scores

Best practices

• Start with a baseline assessment to establish context before large-scale changes
• Adjust dimension weights to align with domain priorities (e.g., reliability for finance)
• Prefer incremental improvements; break large risks into small, scoped tasks
• Combine metric-driven findings with domain knowledge—avoid metric worship
• Run assessments regularly and track trends rather than single-point snapshots

Example use cases

• Assess payment-core system and produce a one-page health report with top 5 actions
• Batch-evaluate a set of services and output a ranked governance backlog for Q2
• Create a governance sprint plan estimating work effort and owners for high-risk items
• Generate a monthly architecture governance summary highlighting trend changes
• Support architecture review by providing risk context and recommended mitigations