jp-summary

Name: jp-summary
Availability: InStock
Author: JingleManSweep

Aggregate phase artifacts into a structured Phase Summary document.

Updated Feb 26, 2026

Search Tags:#workflow #documentation #report #project-management #summarize #phase

Ready to run

npx skills add https://github.com/jinglemansweep/agent-resources --skill jp-summary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jp-summary
Source: https://github.com/jinglemansweep/agent-resources/tree/main/plugins/jplan/skills/jp-summary
Command: npx skills add https://github.com/jinglemansweep/agent-resources --skill jp-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This standalone skill reads end-of-phase artifacts (PRDs, task lists, changelogs, reviews, and fixes) and compiles them into a single, consumable Phase Summary document for stakeholders.

Core Features & Use Cases

Aggregates phase artifacts from execution directories into a single summary.md.
Produces a structured report including project overview, task execution, file changes, review rounds, known issues, and decisions.
Use case: After completing a phase, generate a Phase Summary to archive outcomes and inform stakeholders.

Quick Start

Run /jp-summary [phase-path] to generate the Phase Summary for the specified phase.

Frequently Asked Questions about jp-summary

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

FAQPage Schema

How do I generate a phase summary report from project artifacts?▼

To generate a phase summary report, run the /jp-summary command with the specified phase path. It aggregates PRDs, task lists, changelogs, and reviews into a single summary document for stakeholder review.

What is a phase summary document used for in project management?▼

A phase summary document is used to archive project outcomes and inform stakeholders. It compiles execution artifacts like goals, task statuses, file changes, review rounds, and decisions into one consumable report.

Can I compile a changelog and task list into a single stakeholder report?▼

Yes, you can compile a changelog and task list into a single stakeholder report. The tool extracts project context, file manifests, and review history from phase directories to produce a comprehensive summary.

What's the best way to document project decisions and known issues after a phase?▼

The best way to document project decisions and known issues is generating a phase summary. It captures completed tasks, file changes, review history, and decisions, satisfying the requirement to read and extract phase artifacts.

Do I need completed phase directories to generate a project summary?▼

Yes, completed phase directories are required to generate a project summary. The process applies to completed phases that produce PRDs, tasks.yaml, changelog, reviews, and state history for archival.