health

Compute multi-dimensional project health scores from backlog, reviews, tests, and tracing data.

Updated Aug 27, 2026

Search Tags:#metrics #dashboard #backlog #traceability #sdlc #health #risk

Ready to run

npx skills add https://github.com/tjisousa/gensem --skill health-tjisousa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: health
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/health
Command: npx skills add https://github.com/tjisousa/gensem --skill health-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Health dashboards provide a concise, actionable view of project health across multiple dimensions, enabling teams to spot risks early and align on corrective actions without manual reconciliation.

Core Features & Use Cases

Multi-dimensional health: 8 dimensions in Full mode, 3 in Lightweight, with mode-driven behavior.
Prerequisite-driven insights: reads status/config/backlog to compute scores and trends.
Actionable outputs: generates risk alerts and supports sprint planning, reviews, and governance.

Quick Start

Invoke the health dashboard using /gse:health to display the current multi-dimension project health view.

Frequently Asked Questions about health

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

FAQPage Schema

How do I calculate a multi-dimensional software project health score for sprint planning?▼

A software project health score aggregates backlog, review, test, and tracing data to compute 0-10 scaled results across 8 dimensions. This informs risk assessment and governance during sprint planning and post-release retrospectives.

What is the difference between Full mode and Lightweight mode for project health metrics?▼

Full mode project health metrics display 8 dimensions, while Lightweight mode displays 3. Mode-driven behavior is determined by reading the .gse/config.yaml file, allowing teams to scale dashboard depth based on governance needs.

How do I track design debt and test coverage trends for microservices releases?▼

Track design debt and test coverage trends by optionally reading docs/health-history.yaml for historical data. The system generates trend data and risk alerts to support post-release retrospectives across microservices.

Do I need specific YAML configuration files to generate software risk alerts and health dashboards?▼

Generating software risk alerts and health dashboards requires reading .gse/config.yaml for mode, .gse/status.yaml for scores, and .gse/backlog.yaml for task statuses. Optionally, docs/health-history.yaml provides trend data.

What's the best way to visualize code hygiene and backlog traceability for software governance?▼

Visualizing code hygiene and backlog traceability for software governance is best done via an 8-dimension health dashboard. It aggregates tracing and backlog data into 0-10 scaled results, generating actionable risk alerts.