Gherkin Ticket — Use-Case-First Ticket Authoring

Every ticket must open with a use case a stranger can understand: who gets what outcome, under what condition, and why. Most tickets fail this — they dive straight into implementation ("Wire HRW ownership into dispatchTriage") and the reader has to reverse-engineer the point. This skill fixes that at authoring time.

This skill owns ticket format (title voice + body structure). It does not own the Linear CLI mechanics — once a draft is ready, hand off to the /catalyst-dev:linear skill to actually create or update the issue. CLI syntax lives in /catalyst-dev:linearis.

Paths. Commands below name files inside this skill's own directory as ${CLAUDE_SKILL_DIR}/…. Claude Code fills that in. On any other harness, set CLAUDE_SKILL_DIR to the absolute directory that contains this SKILL.md before running them. If you cannot, stop and report skill_dir_unresolved.

When this fires

Auto-invoked whenever a ticket is being born or rewritten — you do not need to say "gherkin":

• "file a ticket for X", "create tickets for A and B", "open an issue", "log this bug"
• breaking a PRD/plan into tickets
• "rewrite this ticket", "clean up these ticket titles", "this backlog is unreadable"

If the user is mid-creation in another skill (linear, phase-triage), apply these rules to the title and body before the issue is written.