session-documenter
Session documentation workflow.
What this skill does
# Session Documenter Skill Document work, decisions, and context with explicit commands. ## Contract Inputs: - Current session context - Files changed, decisions made, blockers, and next steps - Optional task or PRD references Outputs: - Appended session entry in `.agents/SESSIONS/YYYY-MM-DD.md` - Related summary/task updates when needed Creates/Modifies: - `.agents/SESSIONS/` daily session file - `.agents/memory/*.md` when a decision changes durable project context (architecture, deployment, migrations, gotchas) External Side Effects: - None Confirmation Required: - Before rewriting existing session history - Before promoting session notes into permanent rules or skills Delegates To: - `rules-capture` for reusable preferences discovered during the session - `skill-capture` for reusable workflows discovered during the session - `session-end` for wrap-up flow ## Commands | Command | Action | |---------|--------| | `/start` | Begin new session - creates/appends to today's file, loads context | | `/end` | Finalize session - writes entry with all tracked work, updates related files | ## How It Works 1. **`/start`** - Creates `.agents/SESSIONS/YYYY-MM-DD.md` if missing, or loads existing context 2. **During session** - You tell me what to track: decisions, files changed, mistakes 3. **`/end`** - I write the full session entry with flowcharts, decisions, next steps ## Critical Rules ### Session File Naming (ONE FILE PER DAY) ``` ✅ CORRECT: .agents/SESSIONS/2025-11-15.md ❌ WRONG: .agents/SESSIONS/2025-11-15-feature-name.md ``` Multiple sessions same day → Same file, Session 1, Session 2, etc. ### Flowcharts (MANDATORY for features) Include flowchart for: - New features - Feature modifications - Multi-component bug fixes ## Session Entry Structure 1. **Session number and title** 2. **System flow diagram** (mermaid or text) 3. **Affected components** (frontend, backend, data, external) 4. **What was done** (task checklist) 5. **Key decisions** (with rationale) 6. **Files changed** 7. **Mistakes and fixes** 8. **Next steps** ## Related Files to Update - `.agents/memory/*.md` — when a decision changes durable repo context (architecture, deployment, migrations, gotchas). Bump the file's `last_verified` date when you touch it. ## References - [Full guide: Phases, automation, validation, examples](references/full-guide.md)
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.