// Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures, ensuring root-cause understanding before implementation
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you don't know about. Triggers on questions like "How do I use X library?", "What's the API for Y?", "Show me how Z library handles this", or when encountering unfamiliar library usage.
| name | changelog |
| description | Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering. |
Based on Keep a Changelog.
## [X.Y.Z] - YYYY-MM-DD
### Added/Changed/Fixed/Removed
- **`item-name`** - Description of change
- Sub-bullet for additional details
- Another detail if needed
**\item-name`**` (backticks inside bold)- between item name and descriptionOnly include sections with content.
Good:
- **`debug plugin`** - Renamed skill: systematic-debugging → debug
- **`/workflows:plan` command** - Interactive Q&A refinement phase (#88)
- After generating initial plan, now offers to refine with targeted questions
- Asks up to 5 questions about ambiguous requirements
Bad:
- debug plugin - renamed skill # missing bold/backticks
- **debug plugin**: renamed skill # colon instead of dash
- **`debug plugin`** - renamed skill. # has period