aggregate

Aggregates learnings and retrospective insights from registered projects into a central knowledge base.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill aggregate-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aggregate
Source: https://github.com/fryanpan/ai-team-lead/tree/main/.claude/skills/aggregate
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill aggregate-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running multiple projects in parallel, each project accumulates its own learnings and retrospective notes, but that knowledge stays siloed. This Skill consolidates those insights into a single aggregation log so cross-project patterns become visible and reusable. ## Core Features & Use Cases - Cross-Project Collection: Reads learnings and retrospectives from every project listed in registry.yaml, respecting aggregate: false exclusions to keep client engagements isolated. - Deduplication & Freshness: Pulls each project's latest main branch and compares against the existing aggregation log to avoid duplicate entries. - Pattern Detection: Identifies cross-cutting patterns (recurring failures, slow tasks, skill gaps) and reconciles them against templates and the propagation log before recommending action. - Use Case: Run weekly to merge a dozen project retros into docs/process/aggregation-log.md, then hand off flagged patterns to a propagation workflow that updates shared skills and templates. ## Quick Start Run the aggregate skill to pull the latest learnings and retros from all registered projects into the central aggregation log.

Frequently Asked Questions about aggregate

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

FAQPage Schema
How do I consolidate learnings from multiple projects into one file?▼

Run the aggregate skill, which reads registry.yaml for project paths, pulls each project's learnings and retrospective docs, and appends new dated entries to docs/process/aggregation-log.md. Entries already present in the log are skipped to avoid duplication.

How do I exclude client projects from cross-project knowledge aggregation?▼

Set aggregate: false on the project's entry in registry.yaml. The skill removes those entries before reading any files, so client learnings and retros never reach the shared aggregation log.

What happens if a project's git pull fails during aggregation?▼

The skill runs git pull --ff-only on each project's main worktree. If the pull fails due to a dirty worktree or non-fast-forward state, it warns the user, notes the discrepancy, and reports freshness status before proceeding.

How are cross-cutting patterns identified across projects?▼

The skill scans aggregated entries for recurring failures, slow tasks, successful patterns, and skill gaps. Before flagging a pattern for propagation, it checks templates/skills, templates/rules, the propagation log, and installed shared plugins to avoid re-flagging resolved issues.

Does the aggregation log get committed automatically?▼

Yes. After appending new entries, the skill commits docs/process/aggregation-log.md with the message 'knowledge: aggregate learnings from [N] projects', then summarizes entry counts, patterns, and recommended propagation actions.