minutes-tag

## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.agents/skills/minutes" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-tag" ``` # /minutes-tag Lightweight outcome tagging — adds an `outcome:` field to a meeting's frontmatter so `/minutes-mirror` can correlate the user's behavior with their results over time. The whole point of this skill is **speed**. Tagging should take 5 seconds, not 5 questions. Don't be precious about it — most users will never adopt tagging if it feels like data entry. ## How it works ### Phase 1: Identify the meeting Three patterns the user might use. **Always filter to meetings, not voice memos** — voice memos can't be "won" or "lost". **1. Most recent** ("tag this meeting", "mark that as a win", "tag the call I just finished"): ```bash minutes list --content-type meeting --limit 1 ``` Use the most recent. **Don't ask which one** — that defeats the speed promise. The default behavior should always be "the call you just had". **2. By date** ("tag yesterday's call", "tag the Tuesday call"): ```bash minutes list --content-type meeting --limit 10 ``` Pick the meeting matching the date. If multiple meetings match the same day, ask once: "You had <N> meetings <date>. Which one?" with options listing titles. **3. By name** ("tag my call with Sarah as a win"): ```bash minutes search "<name>" --content-type meeting --limit 5 ``` Pick the most...