Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From execution-skills
Cross-references recent shipped tickets against help center, changelog, and Drive docs to detect outdated articles, missing docs, and stale UI references. Suggests updates and drafts copy.
npx claudepluginhub amplitude/builder-skills --plugin execution-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/execution-skills:update-knowledge-baseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Automatically detect what your docs are missing — and draft the updates.**
Generates polished user-facing release notes from completed Linear, Jira, or GitHub Issues tickets: filters visible changes, groups by product area, saves .docx to Google Drive before releases or weekly.
Generates user-facing release notes from tickets, PRDs, changelogs, or Git logs. Organizes into categories like new features, improvements, bug fixes for product announcements.
Generates user-facing release notes from tickets, PRDs, or changelogs. Categorizes changes into new features, improvements, fixes for announcing updates.
Share bugs, ideas, or general feedback.
Automatically detect what your docs are missing — and draft the updates.
Every release creates documentation debt. This skill reads your latest shipped tickets, compares them against your help center and changelog, and tells you exactly which articles are stale, which features are undocumented, and what to write.
/schedule
### Step 1 — Read recent shipped work
Check {{TICKET_SOURCES}} for items shipped, done, or merged in the past {{TIME_WINDOW}}.
For each: feature name, 1-sentence description of what changed for users, affected product area.
### Step 2 — Read current documentation
- Help center: {{HELP_CENTER_URL}}
- Changelog: {{CHANGELOG_URL}}
- Drive docs at {{DOCS_FOLDER}} modified in the last 90 days
### Step 3 — Detect gaps
**Outdated articles** — docs describing a flow that has since changed
**Missing articles** — features shipped with no documentation
**Stale UI references** — articles mentioning UI elements that no longer exist
### Step 4 — Write update suggestions
For each gap:
**[Article title or "New article needed"]**
Status: Outdated / Missing / Stale UI reference
Affected feature: [from ticket]
What changed: [1 sentence — now vs. what docs say]
Suggested update: [draft the updated paragraph if possible]
### Step 5 — Save
DocUpdates_YYYY-MM-DD.md to {{OUTPUT_FOLDER}} with summary table at top:
| Article | Status | Priority | Suggested action |
Priority: Missing docs for major features = High. Outdated steps = High. Minor wording = Low.
Return the Drive link when done.
| Field | Value |
|---|---|
| MCPs required | Linear / Jira / GitHub Issues, Google Drive, Browser |
| Output | DocUpdates_YYYY-MM-DD.md → /Product/Docs/Updates |
| Scheduler | Weekly, or after each release |
{{TIME_WINDOW}} — e.g. the past 7 days{{TICKET_SOURCES}} — e.g. Linear, Jira, GitHub Issues{{HELP_CENTER_URL}} — e.g. https://help.yourproduct.com{{CHANGELOG_URL}} — e.g. https://yourproduct.com/changelog{{DOCS_FOLDER}} — e.g. /Product/Docs{{OUTPUT_FOLDER}} — e.g. /Product/Docs/Updatesrelease-notes-generator — run both after every release.