groove-utilities-memory-retrospective
Analyse workflow trends: session ratings, recurring mistakes, and learnings over a period. Use for weekly or monthly reflection.
What this skill does
# groove-utilities-memory-retrospective Use $ARGUMENTS to specify period: `week` (default), `month`, or `all`. ## Outcome A period retrospective is output to the conversation: session rating trend, recurring mistake patterns, top learnings captured, and a short workflow health summary. No files are written. ## Acceptance Criteria - Session ratings trend shown (if `learned/signals.md` has data) - Mistake patterns summarised (from resolved incidents in task backend) - Top learnings listed by topic (from `learned/*.md` dated entries) - Workflow health summary: one sentence on overall trend - All output goes to conversation only ## Steps 1. Memory path is always `.groove/memory/` 2. Determine date range from $ARGUMENTS: - `week`: last 7 days (today - 7) - `month`: last 30 days - `all`: all available data - Default if absent: `week` 3. **Session ratings** — read `.groove/memory/learned/signals.md` if it exists: - Parse table rows matching the date range: `| YYYY-MM-DD | N/5 | context |` - Compute: count, average rating, trend (last 3 vs first 3 if enough data) - If no data: note "No session ratings recorded yet" 4. **Mistakes** — query the task backend for resolved incidents under "Groove Memory" → "Mistakes": - `beans list --parent <mistakes-epic-id> -t bug -s completed` for resolved; `-s in-progress` for open - Group by title keywords to identify recurring patterns - Count total resolved vs open incidents - If no task backend or no data: note "No incidents recorded yet" 5. **Learnings** — glob `.groove/memory/learned/*.md` (exclude `signals.md`): - For each file: read and collect dated entries (`## YYYY-MM-DD` headings) within the date range - Group by topic (filename stem) - Count entries per topic; show the most recent bullet per topic as a sample - If no files: note "No learnings captured yet" 6. **Git activity** — run `git log --oneline --since="<start-date>"` to count commits in the period as a proxy for work volume 7. Output retrospective to conversation in this format: ``` ## Groove Retrospective — <period> (<start-date> to <today>) ### Session Ratings <count> sessions rated | avg: <N>/5 | trend: <up/down/flat or n/a> <sparkline of ratings if ≥3 data points, e.g. ▂▄█▆▇> ### Mistakes <N> incidents resolved | <N> open Top patterns: - <root cause pattern> (N occurrences) - ... (No recurring patterns) if all unique ### Learnings <N total entries across <M> topics> - patterns (<N> entries): <most recent bullet> - anti-patterns (<N> entries): <most recent bullet> - ... ### Workflow Health <git commits in period> commits | <1-sentence summary of overall trend> e.g. "Stable week — ratings above 4, one incident (resolved), 3 new patterns captured." ``` ## Sparkline generation Use block characters to render a simple ratings sparkline: - 1/5 → ▁, 2/5 → ▂, 3/5 → ▄, 4/5 → ▆, 5/5 → █ - Only show if ≥ 3 ratings in the period ## Constraints - Read only — do not write to any file - If a data source file is absent, skip that section gracefully with a one-line note - Parse table rows defensively: skip malformed rows rather than erroring - Date filtering: match rows where the `YYYY-MM-DD` date falls within the range; skip rows without a valid date - Output to conversation only — never write to AGENTS.md or memory files
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.