update-changelog
Append phase completion details or final summary to changelog.md during implementation
What this skill does
# Update Changelog
Append phase tracking or final summary to `thoughts/NNNN-description/changelog.md`.
## When to Use
**During Implementation** (after each phase):
- Document what was actually done vs planned
- Note deviations and reasons
- List files changed
- Capture discoveries
**At Completion** (after all phases):
- Append FINAL SUMMARY section
- Summarize key deviations
- Document lessons learned
- Note technical debt and follow-up work
## Phase Update Format
Use template from `templates/changelog-document.md` Phase section:
```markdown
## Phase {N}: {Phase Name}
**Completed**: {ISO_DATE}
**Status**: โ
Complete
### What We Did
- Created slug determination skill
- Added interactive prompting with suggestions
### Deviations from Plan
- **Planned**: Create bash script only
- **Actually**: Created both skill and script
- **Reason**: Skill needed for integration with commands
### Files Changed
- `skills/determine-feature-slug/SKILL.md` - New skill file
- `scripts/next-feature-slug.sh` - Helper script
### Discoveries
- Bash parameter expansion handles leading zeros: `10#$NUM`
- Kebab-case validation regex: `^[a-z0-9-]+$`
```
## Final Summary Format
Use template from `templates/changelog-document.md` FINAL SUMMARY section:
```markdown
## ๐ฏ FINAL SUMMARY
**Completion Date**: 2026-02-05
**Overall Status**: โ
Complete
### What Was Built
Full plugin restructuring with feature directories, changelog tracking,
milestone grouping, and agent orchestration.
### Key Deviations
1. Added interactive slug prompting (not in original plan)
2. Kept thoughts/notes/ unchanged instead of moving
### Impact on Original Plan
- Plan estimated 11 phases, completed 11
- Added 2 skills not in plan (prompting helpers)
- Simplified 3 phases by combining related changes
[... rest of sections ...]
```
## Important Guidelines
- **Read plan first** to understand what was intended
- **Compare actual vs planned** - be specific about deviations
- **Capture learnings** - what would you do differently?
- **Note technical debt** - what was compromised for speed?
- **Append only** - never modify previous phase entries
- **Be concise** - focus on what matters, skip obvious details
## Auto-Correction Loop
The changelog enables auto-correction:
1. Before Phase N: Read both `plan.md` AND `changelog.md`
2. Plan shows original intent
3. Changelog shows actual state after Phase N-1
4. Adapt Phase N approach based on actual state
5. After Phase N: Document new deviations
Example:
```
Phase 3 needs to integrate with auth system
- plan.md says: "Use middleware pattern from Phase 1"
- changelog.md says: "Phase 1 used decorator pattern instead"
- Agent adapts: Uses decorator pattern, not middleware โ
```
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.