Delegate independent tasks to specialized agents working concurrently with isolated context.
project-orchestrator:changelog
Use when completing changes to any service - ensures standardized changelog entries with correct format, location, and content.
SKILL.md
Full skill instructions
Changelog
Overview
Write standardized changelog entries after completing changes. Focus on WHY not WHAT.
Config Loading
- Check if
.project-orchestrator/project.ymlexists - If yes: use
config.services[name].changelogfor the correct file path - If no: look for
CHANGELOG.mdin the service directory or project root
When to Trigger
After completing:
- Bug fixes
- New features
- Refactors affecting behavior
- API changes
- Configuration changes
Skip for: typo fixes, comment-only changes, test-only changes
Format
### YYYY-MM-DD - Brief Title
**Summary:** One-line description.
**What prompted the change:**
- Motivation or problem
**Problem solved:**
- What this enables
Location
Write to the affected service's changelog path from config.services[name].changelog.
If no changelog path is configured:
- Check if
{service_path}/CHANGELOG.mdexists - If not, check if
CHANGELOG.mdexists at project root - If neither exists, ask the user where to write the entry
Multiple services? Write entry to EACH affected service's changelog.
Checklist
- Date format: YYYY-MM-DD (not "Jan 17")
- Title: Brief, describes outcome (not implementation)
- Summary: One line, WHY not WHAT
- Prompted: What problem existed
- Solved: What's now possible
- 10-20 lines max
- Written to correct service changelog
Red Flags
| Bad | Good |
|---|---|
| "Updated code" | "Fix bookmark sync failing silently" |
| "Fixed bug" | "Prevent duplicate records on import" |
| Lists files changed | Explains behavior change |
| 50+ lines | 10-20 lines |
| Entry in root README | Entry in service CHANGELOG.md |
Example
### 2026-01-17 - Fix SSE reconnection dropping notifications
**Summary:** SSE connections now preserve undelivered notifications during reconnect.
**What prompted the change:**
- Users reported missing notifications after connection drops
**Problem solved:**
- Notifications queue during disconnect and deliver on reconnect
More Other skills
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
theme-factory
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Fundamental design principles for writing maintainable, testable Python code.
responsive-design
Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.
Generate Playwright tests from scenarios using interactive browser exploration and validation.
Automated website exploration and test case generation using Playwright.
Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.
gdpr-data-handling
GDPR-compliant data handling with consent management, data subject rights, and privacy controls.
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
refactor-plan
Detailed multi-file refactor planning with safety checks and rollback guidance.
