writing-tickets
Use when you have a spec or requirements for a multi-step task, before touching code
writing-clearly-and-concisely
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-tickets
Use to implement tickets created by writing-tickets skill
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code