session-reviewlisted

# ASK Session Review Two modes: session self-review (primary) and general issue filing (fallback). ## Session Review Mode Use at session close to evaluate whether the skill ecosystem served the work well. 1. Review which skills were loaded during the session from `matchedSkills` in session state. 2. For each used skill, check: did it trigger at the right time? Was its guidance complete? Was anything missing? 3. If a gap, missing trigger, or improvement opportunity emerges → create issue in `MarkBovee/agent-skills-kit`. 4. Issue title starts with `skill:` and names the skill plus the gap (e.g. `skill: session-review lacks triggers for self-review`). 5. Body includes: observed pattern, why current behavior falls short, proposed change. 6. Before filing, check for equivalent open issues with `gh issue list --search` against `MarkBovee/agent-skills-kit`. 7. If improvement is confirmed, flag `shouldCaptureImprovement: true` in session state. ## Evidence-aware issue communication When writing an issue, follow the shared evidence-aware policy: - Establish current state from the complete available context before describing a gap. - Distinguish observed evidence, conclusions, and information still needed. - Keep the workflow phase explicit when a report has moved into implementation, release, or verification. - Ask for new evidence only when a changed version, configuration, or environment makes a fresh capture necessary; explain what it will verify. - Prefer the smallest concr