summarize

To summarize project artifacts and pull requests, provide the artifact path or let the system auto-detect available artifacts. The Skill distills plans, swarm reports, research, roadmaps, bugs, and PRs into concise, human-readable narratives for quick status reporting and handoffs.

The best way to distill project memory artifacts for a phase-based audit is to use a summarization tool that cross-references content against source artifacts. This validates current state and supports optional archival for completed work, reducing cognitive load during audits.

Yes, you can generate concise summaries from pull requests and bug reports automatically. The Skill analyzes a full spectrum of artifact types, including PRs and bugs, to produce structured, human-readable narratives without exposing the raw underlying artifacts.

Yes, the summarization process validates content against the source artifacts. It verifies and cross-references artifact content to ensure the resulting summaries accurately reflect the actual content and current state of the project memory.

Project artifacts that can be converted into human-readable summaries include plans, swarm reports, research, roadmaps, bugs, speculative work, map-reduce results, unfuck tasks, and pull requests. The system distills these varied formats into structured narratives.

You should archive completed artifacts during project summarization when performing phase-aware auditing workflows. The Skill supports optional archival for completed work, allowing you to prep old artifacts for storage while maintaining concise active status reports.