"Shape every ticket around a scannable use-case before it's filed. ALWAYS use when the user says 'file a ticket', 'create a ticket', 'file tickets for', 'open an issue', 'add a ticket', 'log a bug', or whenever drafting, titling, or rewriting a ticket. Turns vague, implementation-first tickets into an outcome title (<actor> should <outcome> so that <benefit>) plus tiered Gherkin (Given/When/Then) acceptance criteria — even for backend bugs and chores."
$npx -y skills add coalesce-labs/catalyst --skill gherkin-ticketInstalls into the current project.
Run `npx skills use "https://github.com/coalesce-labs/catalyst" --skill "coalesce-labs/catalyst/gherkin-ticket"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/coalesce-labs/catalyst" that are relevant to the current task. Run `npx skills add "https://github.com/coalesce-labs/catalyst"` and select the relevant skills, then follow their instructions.