Perform reflection after completing work to capture learnings in KB. Ensures knowledge is preserved for future sessions. WHEN TO USE: - After completing a ticket (before archiving) - After completing a phase - Before session ends (user says "wrapping up", "stopping for now") - When user says "reflect", "capture learnings", "what did we learn" CAPTURES: - Patterns: problems solved (resolved) OR issues found (open) - Decisions: architectural/design choices made - Code flows: new understanding of codebase - Procedures: repetitive tasks worth documenting - Learnings: in ticket's 5-final.md
Captures learnings after completing work or sessions. Automatically updates knowledge base with patterns, decisions, and code flows when tickets finish, phases complete, or you say "reflect".
/plugin marketplace add jayprimer/pmc-marketplace/plugin install jayprimer-pmc-plugins-pmc@jayprimer/pmc-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Capture learnings and update KB after completing work.
ALWAYS run /pmc:kb first to understand KB structure and document formats.
| Trigger | Scope |
|---|---|
| Ticket complete | Single ticket learnings |
| Phase complete | All phase tickets + integration learnings |
| Session ending | Everything done this session |
| User request | Specific topic or full review |
Ask: Did we solve a problem or find an issue worth documenting?
| Type | Status | When to Create |
|---|---|---|
| Solution | Status: resolved | Fixed a tricky bug, found a workaround |
| Known Issue | Status: open | Found limitation, bug we can't fix now |
Format: See kb/references/pattern-format.md
Ask: Did we make architectural or design decisions?
Format: See kb/references/decision-format.md
Ask: Did we learn how code works that wasn't documented?
Last updated: YYYY-MM-DD markerAsk: Did we do something repetitive that should be a procedure?
Create SOP if:
Ask: Did we do research worth keeping?
Save if:
Always update the ticket's 5-final.md with learnings, revealed intent, and decisions made.
Format: See kb/references/ticket-formats.md (5-final.md section)
When time is short:
Minimum output:
## Session Reflection - YYYY-MM-DD
### Completed
- T0000N: {brief summary}
### Key Learnings
- {insight}
### Open Issues
- {issue} (pattern created: Y/N)
### Next Session
- Start with: {task}
1. Update 5-final.md
└── Learned section
└── Revealed Intent (if any)
2. Check for patterns
├── Problem solved? → 6-patterns/{name}.md (Status: resolved)
└── Issue found? → 6-patterns/{name}.md (Status: open)
3. Check for decisions
└── Design choice made? → 5-decisions/D###-{name}.md
4. Update code map (if learned new code flow)
1. All ticket reflections done?
2. Integration learnings
└── How tickets worked together
└── Unexpected interactions
3. Update 4-status/health.md
└── Test counts
└── Open patterns count
└── Technical debt notes
4. Phase retrospective
└── What worked well
└── What to improve
1. Uncommitted learnings?
└── Anything not yet captured in docs
2. Current state
└── What's in progress
└── What's blocked
3. Next session setup
└── What to start with
└── Any context to preserve
Patterns are for BOTH solutions AND open issues:
| I found... | Create pattern with... |
|---|---|
| Bug fix that was tricky | Status: resolved |
| Workaround for limitation | Status: resolved (document workaround) |
| Bug we can't fix now | Status: open (document for future) |
| Platform limitation | Status: open (document workaround if any) |
| Technical debt | Status: open (document scope) |
Open patterns are valuable - they prevent future developers from wasting time rediscovering known issues.
After reflection, confirm:
## Reflection Complete
### Updated
- [ ] 5-final.md: Learned section
- [ ] 6-patterns/: {N} patterns (X resolved, Y open)
- [ ] 5-decisions/D###-{name}.md: {N} decisions
- [ ] 7-code-maps/: {files updated}
- [ ] 2-sop/: {new procedures}
- [ ] 8-research/: {research saved}
### Open Items
- {Any unresolved issues}
### Next Steps
- {What to do next}
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.