assess-system-health-over-time

Evaluate architectural debt, documentation currency, complexity, and quality metrics over time.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/constellize/marketplace --skill assess-system-health-over-time
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assess-system-health-over-time
Source: https://github.com/constellize/marketplace/tree/main/plugins/constellize-evolution/skills/assess-system-health-over-time
Command: npx skills add https://github.com/constellize/marketplace --skill assess-system-health-over-time

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track long-term system health trends to inform evolution decisions by systematically evaluating architectural debt, knowledge currency (documentation matches reality), areas of increasing complexity, maintenance burden trends, system quality metrics, and health preservation over time.

Core Features & Use Cases

  • Preserves historical system state to answer: Is architectural debt growing or shrinking?
  • Evaluates documentation currency, complexity hotspots, and maintenance burden to prioritize improvements.
  • Generates a Health Assessment pattern, historical comparison, and a concrete health improvement plan for governance.

Quick Start

Run a quarterly health assessment to generate the System Health Assessment and compare it to the previous period.

Frequently Asked Questions about assess-system-health-over-time

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

FAQPage Schema
How do I track architectural debt and system health trends over time?

Track system health by evaluating architectural debt, documentation currency, complexity, and maintenance burden across quarterly milestones to reveal trends and identify priorities for refactoring. This preserves historical state to compare with prior periods.

What is the best way to assess if documentation matches reality during maintenance?

Assess documentation currency by evaluating whether technical docs match the actual system reality as part of a multidimensional health check. This identifies knowledge gaps and prioritizes improvements for governance.

How do I generate a system health improvement plan for governance reviews?

Generate a health improvement plan by running a quarterly assessment that evaluates quality metrics and maintenance burden, then compare results with previous periods to produce concrete refactoring and automation priorities.

Can I use this to find complexity hotspots and maintenance burden trends?

Identify complexity hotspots and maintenance burden by applying systematic evaluations during milestone reviews. The assessment reveals increasing complexity areas and generates historical comparisons to guide evolution decisions.

Does this system health evaluation work for quarterly milestone reviews?

Apply this assessment across quarterly or milestone evaluations to compare with prior periods. It satisfies executive summary requirements by tracking multidimensional health dimensions and revealing long-term architectural debt trends.

Why should I evaluate system health trends instead of just fixing bugs?

Evaluating system health trends informs long-term evolution decisions by revealing whether architectural debt is growing or shrinking, rather than just addressing immediate bugs. This approach prioritizes refactoring, automation, and knowledge improvements.