han-feedback

## Project Context - Today's date: !`date +%Y-%m-%d` # Capture Feedback ## Operating Principles - **The whole han-* family is in scope.** Capture skills and agents from every Han plugin (`han-core`, `han-planning`, `han-coding`, `han-github`, `han-reporting`, `han-feedback`, and any future `han-*` plugin). Skills and agents from non-Han plugins are out of scope. - **Invocations count, not completions.** A skill or agent is considered used if it appeared in the session, regardless of whether it finished or was cancelled. Feedback on a partial run is still feedback. - **Agents count even when a skill dispatched them.** Most Han agents run because a skill dispatched them. Those agents are still in scope; record which ones contributed so the feedback names where specialist value came from. - **Conservative defaults on posting.** The feedback directory is user-space. The posting target is a public GitHub repository. Ambiguous confirmation is treated as a stop, not a go. - **One file per day per run.** Do not overwrite existing feedback for today. If a skill or agent is already covered by a file for today, skip it. - **Compacted sessions limit visibility.** The skill can only see turns present in the context window. If the session was compacted before running this skill, earlier invocations may not be visible. ## Step 1: Identify Han skills and agents used this session Look back through the conversation for any use of a Han plugin component. A component counts as used if it w...