skills.rest
matochu
matochuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro-all

Aggregate feature retrospective data into a persistent project-wide report.

4|Updated Mar 23, 2025
Search Tags:#reports#documentation#collaboration#retrospective#feature-analysis#project-management
One-click install
npx skills add https://github.com/matochu/pythia --skill retro-all
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro-all
Source: https://github.com/matochu/pythia/tree/main/.agents/skills/retro-all
Command: npx skills add https://github.com/matochu/pythia --skill retro-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate or update the consolidated project-level retrospective by aggregating retrospective data across all features (or a specific subset). Output is saved to .pythia/notes/retro-project.md — a single persistent file, updated on each run (new blocks appended, existing blocks never deleted).

Core Features & Use Cases

  • Aggregates multi-feature retros by collecting plan/implementation insights across features into a unified report.
  • Appends new runs to the persistent retro file, preserving history for trend analysis.
  • Supports scoped analysis by feature IDs or date filters and can operate with all features by default.
  • Reference-driven: uses existing notes/retro.md when available and raw sources from plans and reports otherwise.
  • Cross-feature patterns: identifies recurring themes like risks and process improvements.

Quick Start

Run /retro-all to aggregate all feature retros into the persistent retro report.

Frequently Asked Questions about retro-all

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

FAQPage Schema
How do I consolidate feature-level retrospectives into a single project report?▼

You consolidate feature-level retrospectives by aggregating plan, codebase, process, risk, and tooling blocks from plans and implementation reports into one persistent project-wide retro report saved to .pythia/notes/retro-project.md.

How does appending new retrospective runs work for project trend analysis?▼

Appending new retrospective runs adds fresh cross-feature insights to the persistent retro file while preserving existing historical entries, creating a continuous knowledge base for identifying recurring risks and process improvements over time.

What source files are used to generate a cross-feature retrospective report?▼

The cross-feature retrospective report uses existing notes/retro.md as a reference when available, and otherwise collects raw sources from plans/*.plan.md and reports/*.implementation.md files to extract retrospective blocks.

Can I generate a project retrospective for a specific subset of features or date range?▼

Yes, you can scope a retrospective aggregation by passing specific feature IDs or using a --since date filter, allowing you to analyze a subset of features instead of operating across all features by default.

Does the project-wide retrospective report delete previous retrospective entries?▼

No, the project-wide retrospective report never deletes existing entries; it appends new blocks to the persistent retro file, ensuring historical project management data is preserved for long-term analysis.

Related Skills

Explore More Content & Communication Skills→
lluppesmslluppesms

structured-autonomy-generate

Generate implementation documentation with complete code from a PR plan.

Community
Advanced
ambroviaambrovia

compound

Analyze retro log files to identify recurring development frictions across work packages.

Official
Advanced
ioniksioniks
526

markdown-task-manager

Turn local Markdown files into a live Kanban board.

Community
Basic
JingyiWngJingyiWng

bmad-retrospective

Conduct post-epic retrospectives from story files and sprint-status.yaml.

Community
Advanced