Creates or appends to a modpack project dev-log in <project>/docs/dev-log.md. Use when recording changes, decisions, or investigations during modpack curation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bgs-modding-superpowers:writing-modpack-devlogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The modpack dev-log is the durable record of what the curator did to the modpack, in chronological order, with enough context for a future maintainer to understand why a change happened. This skill replaces the deleted `templates/modpack/dev-log.md` template by creating `<project>/docs/dev-log.md` at runtime, then appending entries as the modpack evolves.
The modpack dev-log is the durable record of what the curator did to the modpack, in chronological order, with enough context for a future maintainer to understand why a change happened. This skill replaces the deleted templates/modpack/dev-log.md template by creating <project>/docs/dev-log.md at runtime, then appending entries as the modpack evolves.
| Use this skill when... | Result |
|---|---|
| The user says "log this", "add to dev log", "record what I did", or "note this change" | Append a dated entry to the project dev-log. |
| A mod was added, removed, replaced, upgraded, downgraded, patched, or moved in load order | Record what changed and why. |
| A conflict-audit session finished | Summarize the finding and link evidence from xedit-conflict-audit or xedit-automation output. |
| A CTD, freeze, missing asset, bad facegen, navmesh issue, or broken quest was investigated | Preserve the investigation result, even if the fix is not final. |
| A modpack release was cut | Add the curator-facing note and cross-link to writing-modpack-changelog. |
| The user made a manual decision that future agents must not re-litigate | Record the decision, context, and evidence. |
| Do not use this skill when... | Use instead |
|---|---|
| The user is preparing public release notes for players | writing-modpack-changelog |
| The user asks for a one-off explanation without wanting a project record | Answer directly. |
| The project root is unknown and the user refuses to identify it | Stop after explaining what is missing. |
| The entry would expose private notes, credentials, or personal information | Ask for a sanitized version first. |
| The request is to inspect or edit plugin records | xedit-automation or xedit-conflict-audit first, then log the result. |
<modpack_project_root>, use it.Data/, profiles/, or docs/, default to pwd and tell the user what default you used.<project>/docs/dev-log.md.
<project>/docs/ does not exist, create it.dev-log.md is missing, create it before appending.# <Project Name> Dev LogStarted: <local ISO-8601 timestamp with offset>## Entries2026-06-01T14:30:00-04:00.Mods touched subsection when specific mods, plugins, patches, or tools were involved.Refs subsection linking evidence, logs, issue threads, release pages, or xEdit captures.## Entries section.
## Entries.<existing title> from <timestamp>. Append anyway? (y/N)"<project>/docs/dev-log-artifacts/<entry-slug>/.Refs subsection.| Field | Canonical shape | Example |
|---|---|---|
| File | <project>/docs/dev-log.md | docs/dev-log.md |
| Entry heading | ### <timestamp> - <short title> | ### 2026-06-01T14:30:00-04:00 - Rebuilt settlement patch after lighting update |
| Body | One or more paragraphs explaining what changed and why | Updated the settlement compatibility patch after the lighting mod changed precombines in the affected cells. |
| Mods touched | Optional bullet list | - Example Lighting Overhaul |
| Refs | Optional bullet list of copied artifacts or external references | - dev-log-artifacts/rebuilt-settlement-patch/xedit-conflict-summary.md |
Canonical entry shape:
### 2026-06-01T14:30:00-04:00 - Rebuilt settlement patch after lighting update
Updated the settlement compatibility patch after the lighting mod changed records in the affected cells. The new patch keeps the visual change while preserving the workshop keyword edits from the settlement overhaul.
#### Mods touched
- Example Lighting Overhaul
- Example Settlement Overhaul
- Example Modpack Patch
#### Refs
- dev-log-artifacts/rebuilt-settlement-patch/xedit-conflict-summary.md
Fixed the lighting thing.
This entry has no date, no mod names, no context, no evidence, and no explanation of what was fixed.
### 2026-06-01T14:30:00-04:00 - Resolved lighting and workshop keyword conflict
Kept the lighting overhaul's cell image-space change, but restored the settlement overhaul's workshop keyword edits in the patch. This should preserve the intended visual pass without breaking workshop placement in the affected settlement.
#### Mods touched
- Example Lighting Overhaul
- Example Settlement Overhaul
- Example Modpack Patch
#### Refs
- dev-log-artifacts/lighting-workshop-keyword-conflict/xedit-conflict-summary.md
This entry tells a future curator what changed, why it changed, which mods were involved, and where the evidence lives.
| Excuse | Reality |
|---|---|
| "This is just a tiny note; it does not need structure." | Tiny notes become the only record future agents can trust. Date, title, context, and refs are the minimum useful shape. |
| "The release changelog will cover it." | The changelog is for players. The dev-log is for curators and future agents. They answer different questions. |
| "The evidence is in my terminal scrollback." | Scrollback is not durable. Copy evidence into docs/dev-log-artifacts/<entry-slug>/ and link it. |
| "I can append at the bottom; it is easier." | Newest-first keeps the current state visible. Insert below ## Entries unless the user explicitly chose oldest-first. |
| "The user knows what they meant by 'lighting thing'." | Future maintainers will not. Name the symptom, mod, plugin, cell, record, or decision. |
| "I should ask several questions to make sure the entry is perfect." | Ask once for the project root if needed. Otherwise write the best entry from available context and flag uncertainties inline. |
| "The artifact path is already linked in the conversation." | Conversation links are not project records. Copy or preserve the artifact in the project docs tree. |
| "I should make this sound polished." | Accuracy beats polish. Keep the operational facts and make the wording readable. |
writing-modpack-changelog - use for player-facing release notes and version sections.setting-up-bgs-modding-environment - use when the modpack project structure itself is being created or located.Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub bb-84c/bgs-modding-superpowers --plugin bgs-modding-superpowers