deliverable-monitoring

Interpret deliverable monitoring metrics and recommend interventions for meta-squad teams.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/lygav/vladi-plugins-marketplace --skill deliverable-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliverable-monitoring
Source: https://github.com/lygav/vladi-plugins-marketplace/tree/main/plugins/squad-archetype-deliverable/meta/skills/deliverable-monitoring
Command: npx skills add https://github.com/lygav/vladi-plugins-marketplace --skill deliverable-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interpret deliverable monitoring data and present actionable insights to the meta-squad, helping them understand deliverable-team health and progress.

Core Features & Use Cases

  • Interpret metrics such as fragmentCount, totalFragments, schemaVersion, deliverableSize, validationStatus, and state to assess health.
  • Provide guidance on when to escalate based on stalled progress, invalid validation, or failed merges.
  • Use Case: Teams evaluating sprint deliverables, dashboards explanation, and intervention recommendations.

Quick Start

Provide an interpretation of the latest deliverable-monitoring data and suggest concrete next actions.

Frequently Asked Questions about deliverable-monitoring

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

FAQPage Schema
How do I interpret deliverable monitoring metrics to assess project health?

Deliverable monitoring interprets metrics like fragmentCount, validationStatus, and aggregationProgress by parsing structured data and evaluating a state machine to assess health and recommend interventions.

What do stalled progress and invalid validation statuses mean for sprint deliverables?

Invalid validation and stalled aggregationProgress indicate failed merges or scanning issues, requiring immediate intervention guidance to recover the deliverable state and restore progress.

How can I explain a deliverable health dashboard to my team?

Dashboard explanation involves interpreting structured monitoring data, translating state machine phases like preparing, scanning, and distilling into actionable insights for meta-squad teams.

When should I escalate issues based on deliverable monitoring data?

Escalate when validationStatus is invalid, merges fail, or progress stalls beyond defined thresholds, triggering recovery prompts and concrete next actions to resolve deliverable issues.

Can I use deliverable monitoring for large files with high fragment counts?

Yes, deliverable monitoring handles high fragmentCount and totalFragments by tracking deliverableSize, schemaVersion, and lastFragmentAt to evaluate aggregationProgress and overall state.