reflect

Name: reflect
Availability: InStock
Author: jayprimer

Capture completed work learnings and commit them to the knowledge base.

Updated Jan 4, 2026

Search Tags:#documentation #learning #patterns #retrospective #knowledge-base #reflect

Ready to run

npx skills add https://github.com/jayprimer/pmc-marketplace --skill reflect-jayprimer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/jayprimer/pmc-marketplace/tree/main/plugins/pmc/skills/reflect
Command: npx skills add https://github.com/jayprimer/pmc-marketplace --skill reflect-jayprimer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform reflection after completing work to capture learnings in KB. Ensures knowledge is preserved for future sessions.

Core Features & Use Cases

Capture patterns, decisions, code flows, procedures, and learnings from tickets and phases.
Update the knowledge base to preserve institutional knowledge for future teammates and sessions.
Use cases include post-ticket retrospective, phase wrap-up, and end-of-session reviews.

Quick Start

After a ticket or phase completes, run /pmc:reflect to capture learnings into the knowledge base.

Frequently Asked Questions about reflect

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

FAQPage Schema

How do I capture learnings and document patterns after completing a ticket?▼

To capture learnings after ticket completion, run a retrospective process that documents patterns, decisions, code flows, and procedures, then commits those structured entries directly into the knowledge base to preserve institutional knowledge for future sessions.

What is the best way to preserve knowledge at the end of a working session?▼

The best way to preserve knowledge at session end is to perform a reflection that extracts procedures and learnings from completed work, generating structured outputs and knowledge base entries that ensure knowledge is preserved for future teammates and sessions.

Do I need to manage the knowledge base before running a retrospective?▼

Yes, you must run the knowledge base management command first to establish prerequisites before capturing learnings, ensuring the reflection process can successfully commit patterns, decisions, and procedures into properly structured knowledge base entries.

Can I use this to document code flows and decisions during a phase wrap-up?▼

Yes, you can document code flows and decisions during a phase wrap-up by applying the reflection process after phase completion, which captures structured learnings and updates the knowledge base to maintain institutional knowledge across project phases.

What happens to learnings if I skip the retrospective after finishing work?▼

If you skip the retrospective, learnings from completed work are not committed to the knowledge base, meaning patterns, decisions, and procedures risk being lost for future sessions and teammates who need that institutional knowledge.