AgentSkillsCN

lifecycle-health-monitor

在项目全周期内持续监测项目健康状况，重点关注规格漂移与技术债务积累。此技能适用于定期项目评审环节。

SKILL.md
--- frontmatter
name: lifecycle-health-monitor
description: Monitors overall project health across time, specifically looking for spec drift and debt. Use during regular project reviews.
triggers: [periodic-review, milestone-completion, project-health-check]
outputs: [health-report, risk-escalation]

Lifecycle Health Monitor

Purpose

Provides a macro-view of the project's long-term viability. It detects "rot" in the form of outdated specs, falling test coverage, or increasing complexity that slows down development.

When to use this skill

  • •During monthly or quarterly project reviews
  • •After reaching a major milestone
  • •When development velocity noticeably drops

Monitoring Steps

  1. •Evaluate Spec Drift: Compare the latest implementation_plan.md files against the master spec. Are updates being backported?
  2. •Evaluate Test Coverage Relevance: Is coverage high in critical logic areas, or just in utility functions?
  3. •Evaluate Orchestration Efficiency: Are certain skills being bypassed or overridden frequently? (Inputs from skill-evolution-engine).
  4. •Flag Systemic Risks: Look for single points of failure in the architecture or process.

Decision Tree

mermaid
flowchart TD
    A[Check Project Health] --> B{Spec vs Code Gap?}
    B -->|Large| C[Alert: Critical Spec Drift]
    B -->|Small| D{Test Coverage Adequate?}
    D -->|No| E[Alert: High-Risk Implementation]
    D -->|Yes| F{Orchestration Fluid?}
    F -->|No| G[Trigger Skill Refinement]
    F -->|Yes| H[Report: Healthy Status]

Review Checklist

  1. •Aging: Are there tasks that have been "in progress" for more than 2 weeks?
  2. •Quality: Is the bug-fix vs new-feature ratio increasing?
  3. •Documentation: Is the README.md and SKILL_INDEX.md up to date?
  4. •Alignment: Does the current implementation still match the Project Vision?

How to provide feedback

  • •Be specific: "Spec drift detected in the Payment module; 3 new fields added to code are not in the spec."
  • •Explain why: "Outdated specs lead to incorrect test generation and security misses."
  • •Suggest alternatives: "Recommend a spec-auto-updater session for the Payment module."

Healthy systems age gracefully.