ddd-weekly-report

Generate weekly DDD reports from changelogs and health documents.

36|4|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/xg-gh-25/SwarmAI --skill ddd-weekly-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-weekly-report
Source: https://github.com/xg-gh-25/SwarmAI/tree/main/backend/skills/s_ddd-weekly-report
Command: npx skills add https://github.com/xg-gh-25/SwarmAI --skill ddd-weekly-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates DDD cultivation activity into a concise weekly narrative, helping leaders identify growth areas, decisions, and stale documents across projects.

Core Features & Use Cases

  • Cross-project aggregation of DDD documents and changes
  • Executive-level summary with decisions needed and upcoming actions
  • Health dashboard per project showing document status, freshness, and evolution

Quick Start

Run the DDD weekly report for all projects to summarize the past seven days of changes.

Frequently Asked Questions about ddd-weekly-report

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

FAQPage Schema
How do I generate a cross-project weekly report for DDD document changes?

To generate a weekly DDD report, the skill aggregates document changes across all projects by reading ddd-changelog.jsonl and proposal JSON files, then saves an executive summary and health dashboard to Knowledge/Reports/YYYY-MM-DD-ddd-weekly.md.

What is a DDD health dashboard and how does it track project status?

A DDD health dashboard tracks project document status, freshness, and evolution. This skill computes it per project by analyzing health-stat documents and changelog data to identify stale documents and growth areas.

How do I consolidate decisions-needed and upcoming actions from multiple project proposals?

Consolidating decisions-needed involves aggregating proposal JSON files from Projects/*/.artifacts/proposals/ across all projects. This skill extracts pending decisions and upcoming actions into an executive-level summary within the weekly report.

Can I use this weekly reporting skill if my projects lack .artifacts directories?

You cannot use this skill without .artifacts directories, as it strictly reads from Projects/*/.artifacts/ddd-changelog.jsonl and proposals/*.json. You must configure your projects to output these artifact files for the report to compute.

What's the best way to summarize seven days of DDD cultivation activity for leadership?

The best way to summarize DDD cultivation activity is generating a weekly report that cross-references changelog and health data. This skill produces a concise narrative highlighting growth areas, stale documents, and executive decisions.

Why does my weekly DDD report fail to capture health statistics correctly?

Your weekly DDD report fails when health-stat documents are missing or improperly formatted. The skill requires valid health-stat files alongside ddd-changelog.jsonl in the project .artifacts directory to compute document freshness and evolution metrics.