メニュー
Generate a changelog entry from commits, PRs, or a description of changes. Follows Keep a Changelog format with clear, user-facing language. TRIGGER when: user says /changelog, needs release notes, wants to summarize recent changes, or is preparing a release.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Model financial scenarios — base, upside, and downside cases with revenue, cost, and cash flow projections. Produce scenario comparison tables with sensitivity analysis. Finance-specific scenario planning distinct from strategy-level scenario planning. TRIGGER when: user says /financial-scenario-planning, "financial scenario", "financial modeling", "scenario model", "stress test financials", or asks to model financial outcomes under different assumptions.
Develop scenario plans with multiple futures, key uncertainties, signposts, and strategic responses for each scenario. Structure scenario analysis for strategic decision-making. TRIGGER when: user says /strategic-scenario-planning, "scenario planning", "scenario analysis", "what-if analysis", "strategic scenarios", "contingency planning".
Package a support escalation for engineering or management with full context, timeline, business impact, and recommended actions. TRIGGER when: user says "escalate", "escalation", "needs engineering", "needs management", "critical issue", "P0", "P1", "sev1", "sev2", "customer at risk", "churn risk", "executive escalation", or "get engineering involved".
Research a customer issue across all available sources — tickets, documentation, logs, account data, and internal knowledge — to build a complete picture before responding or escalating. TRIGGER when: user says "research customer", "investigate issue", "look into this ticket", "find context", "customer history", "what do we know about", "pull up account", "dig into this", "gather context", or "background on this customer".
Draft a customer-facing support response that is empathetic, clear, and solution-oriented. Matches tone to the situation and follows communication best practices. TRIGGER when: user says "draft response", "draft reply", "write response", "reply to customer", "respond to ticket", "write back", "craft response", "help me reply", "customer email", or "what should I say".
Turn a resolved support ticket or commonly reported issue into a polished, self-service knowledge base article that reduces future ticket volume. TRIGGER when: user says "kb article", "knowledge base", "write an article", "document this", "help article", "FAQ entry", "self-service", "deflection article", "create documentation for this issue", or "turn this into a doc".
| name | changelog |
| description | Generate a changelog entry from commits, PRs, or a description of changes. Follows Keep a Changelog format with clear, user-facing language. TRIGGER when: user says /changelog, needs release notes, wants to summarize recent changes, or is preparing a release. |
| argument-hint | [version, date range, or PR list] |
| user-invocable | true |
You are a technical writer creating a changelog entry. Write clear, user-facing descriptions that help users understand what changed and why it matters.
Use Keep a Changelog categories:
For each change:
Good: "Added bulk export for reports — export up to 10,000 records as CSV (#423)" Bad: "Refactored ReportService to use streaming iterator pattern"
## [version] - YYYY-MM-DD
### Added
- Description of new feature (#PR)
### Changed
- Description of change (#PR)
### Fixed
- Description of bug fix (#PR)
### Security
- Description of security fix (#PR)
### Breaking Changes
- Description of breaking change and migration steps (#PR)
A single changelog entry in Keep a Changelog markdown format, ready to prepend to CHANGELOG.md.