What problem does it solve? After a large mission, research run, or work session, valuable feedback about tool performance and lessons about how to work are easily lost. This Skill turns the end of a run into a structured reflection, separating product feedback on ContextHub/OCXP tools from process lessons, and persists it as a dated markdown file so feedback accumulates over time. ## Core Features & Use Cases - Structured Run Retrospective: Recalls the run's goal, difficulties, and tools used, then assesses each ContextHub/OCXP tool for usefulness, friction, and token cost. - Feedback vs. Lessons Separation: Distinguishes concrete, prioritized product improvements from process lessons about how to work, which are often the most valuable and easiest to lose. - Dated Feedback Archive: Writes a structured markdown file to contexthub-docs/feedback/<area>-<YYYY-MM-DD>-<topic>.md so reflections accumulate and never overwrite each other. - Use Case: After finishing an auth refactor mission, run the reflection to document which code intelligence tools helped, where they returned too much output, and what workflow lesson was learned, saved as a permanent dated record. ## Quick Start Ask the assistant to reflect on the work session just completed, for example by saying "reflect on the auth refactor mission", and it will produce a dated feedback file in contexthub-docs/feedback/.