update-dev-docs

Included with Lifetime

$97 forever

Update dev docs before compaction. Use before ending sessions or switching tasks.

General

What this skill does


# Update Dev Docs

Updates the dev docs to capture current progress before session compaction or ending a session.

## When to use

- Before using `/compact` to compress conversation
- Before ending a long session
- When switching to a different task
- Periodically during very long implementations

## Usage

```
/update-dev-docs [task-name]
```

If task-name is not provided, will look for active tasks in `dev/active/`.

## Instructions

When this command is invoked:

1. **Find active dev docs**:
   - Check `dev/active/` for existing task folders
   - If multiple found and no task-name provided, list them and ask which to update

2. **Update tasks.md**:
   - Sync with current TodoWrite state
   - Mark completed items as done
   - Add any new tasks discovered during implementation
   - Update complexity estimates if needed

3. **Update context.md**:
   - Add newly discovered key files
   - Document any new decisions made
   - Update code patterns if new ones were identified
   - Add any gotchas or lessons learned

4. **Update plan.md** (if needed):
   - Update progress on objectives
   - Note any strategy changes
   - Update risk assessment based on discoveries

5. **Generate session summary**:
   - What was accomplished this session
   - What's next
   - Any blockers or open questions

## Session Summary Template

Add to the end of context.md:

```markdown
## Session Log

### [Date] Session

**Accomplished:**

- Item 1
- Item 2

**Next Steps:**

- Item 1
- Item 2

**Blockers/Questions:**

- Question 1
```

## Notes

- Keep updates concise but informative
- Focus on capturing context that would be lost after compaction
- Include specific file paths and line numbers where relevant
- Document "why" not only "what" for decisions

Files: 1

Size: 1.8 KB

Complexity: 4/100

Category: General

Source: https://github.com/htlin222/dotfiles/tree/main/claude.symlink/skills/update-dev-docs

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts