Documentation hooks
| Key | Shape | Default | Purpose |
|---|---|---|---|
docs.updateSkill |
string or null |
null |
Name of a local skill (.claude/skills/<name>/) that updates your documentation for a shipped delta. null means no documentation system; the docs phase reports itself skipped. |
docs.releaseNotesSkill |
string or null |
null |
Name of a local skill that writes and publishes a release note. Used only when you pass --release-notes to the release skill. |
docs.knowledgeBaseSyncSkill |
string or null |
null |
From 3.20.0: a local skill that refreshes a knowledge base (a help centre's copy of your docs) after the documentation was published live. Called with sync and { "docsOutcome", "live" } right after the docs update and only when it published; owed as knowledge-base at the release's hand-back until it runs. First line KNOWLEDGE BASE SYNC: DONE, CURRENT or FAILED; a failure never undoes the documentation push. A bare run is the read-only check. Step: /devstride:sync-knowledge-base. |
docs.updateOnEpicRelease |
boolean | false |
Also run the docs skill when a release-unit pull request merges, not only at the production cut. |
The plugin never edits documentation itself. /devstride:setup asks where your documentation lives, how it is updated, and how release notes are pushed, then scaffolds the two local skills from its templates and writes only their names here. Each skill accepts update (docs) or publish / draft (notes) with a structured delta payload, and a read-only check mode that setup and doctor run. Core documentation is updated by default on every production release (no docs suppresses it); release notes are written only when you pass --release-notes, and only after the production merge is confirmed and the deploy verified — nothing in the loop decides that a release deserves a note. From 3.20.0 the docs step reports what really happened: CURRENT when nothing needed to change, PUBLISHED only on evidence the docs are live, and STAGED for a draft or a docs pull request waiting on the owner, which the recap names as an owner action. A failed docs, knowledge-base or release-notes run stays owed until it succeeds, and each step can be re-run by name (/devstride:update-docs, /devstride:sync-knowledge-base, /devstride:write-release-notes).
release.docsRepo (versions before 1.0.0) is deprecated: the release skill reports it and runs without docs; /devstride:setup docs migrates it into a local skill.