reflect

Features and purpose

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

Quick start

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.