deliverable-aggregation

Aggregate cross-team deliverables with schema validation and manifest generation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinating across domain teams to collect, validate, and merge deliverables into a single, coherent artifact.

Core Features & Use Cases

  • Cross-team deliverable collection from all domain teams after status: complete
  • Schema-based validation with optional import-hook post-processing
  • Manifest generation and audit trail (.squad/aggregation/manifest.json) for traceability

Quick Start

Run the aggregation process to collect and validate all completed team deliverables.

Frequently Asked Questions about deliverable-aggregation

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

FAQPage Schema
How do I aggregate deliverables from multiple teams into a single output?

To aggregate cross-team deliverables, this Skill collects completed work from all domain teams, validates each output against a schema, and merges them into a unified meta-squad result with a generated manifest for traceability.

What is schema-based validation for cross-team deliverable collection?

Schema-based validation is a process that checks each domain team's completed deliverables against a defined structure before merging. This ensures that all aggregated outputs meet consistent formatting and content requirements across the meta-squad.

How do I validate completed team outputs before merging them?

You validate completed team outputs by running the aggregation process, which automatically checks each team's deliverables against a schema and optionally applies an import hook for post-processing before producing the final merged artifact.

Can I use an import hook for post-processing during deliverable aggregation?

Yes, you can use an optional import hook for post-processing during cross-team deliverable aggregation. This allows you to apply custom transformations to the collected outputs after schema validation but before generating the final manifest.

How does cross-team deliverable aggregation track merged outputs?

Cross-team deliverable aggregation tracks merged outputs by generating an audit trail manifest. This manifest is saved as a JSON file in the aggregation directory, providing full traceability for the collection and validation of completed team deliverables.

When do I need to run cross-team deliverable aggregation?

You need to run cross-team deliverable aggregation when one or more domain teams have completed their work and the leadership team needs to validate and merge these individual outputs into a single, coherent meta-squad artifact.