ticket-authoring

rampstackco/claude-skills Product & project management Testing & QA

ticket-authoring is a skill in rampstackco/claude-skills, last changed 19 Oct 2026. It can name web addresses.

From the author

Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.

What it can touch

Names web addresses

How much a skill can do, not whether it is risky.

Pattern check

Nothing flagged

That isn't proof the skill is harmless.

Commit 9b90db2 · 3 Nov 2026

How the check works

Pattern check: nothing flagged

That isn't proof the skill is harmless.

Install

Each tab says whether it installs commit 9b90db2, the one we checked, or the latest version.

OpenCode also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Goose also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Windsurf (Devin Desktop) also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Zed also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Roo Code also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Factory Droid also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Junie also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

Amp also looks in .agents/skills/ and ~/.agents/skills/, so use the Any agent steps.

No install command here reaches Kiro. Copy the skill's folder into .kiro/skills/ in your project, or ~/.kiro/skills/ for all your projects. rampstackco/claude-skills/skills/ticket-authoring (opens in a new tab)

Antigravity also looks in .agents/skills/, so the Any agent steps reach it with This project. For All projects, see where Antigravity looks.

Cline also looks in .claude/skills/, so the Claude Code steps reach it with This project. For All projects, see where Cline looks.

No tab for your agent? Use Any agent for OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie and Amp. With This project, Any agent also reaches Antigravity and Claude Code reaches Cline. Kiro needs the folder copied by hand.

Pinned to commit 9b90db2, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&mkdir -p .claude/skills &&mkdir .claude/skills/ticket-authoring &&cp -R "$tmp"/skills/ticket-authoring/. .claude/skills/ticket-authoring/ &&rm -rf "$tmp"

If Claude Code was already running and this created the skills folder, run /reload-skills.

Or install the rampstack-skills plugin it ships in. Installs the latest version, not the one we checked. Installs everything in the plugin, including any hooks, MCP servers and scripts our check doesn't cover.

claude plugin marketplace add rampstackco/claude-skills --scope project &&claude plugin install rampstack-skills@rampstack --scope project

Claude Code docs

Pinned to commit 9b90db2, the one we checked.

Skills in the Claude apps belong to your account rather than to a project.

Make ticket-authoring.zip, with the skill folder at the top level:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&out="$(mktemp -d)" &&cp -R "$tmp"/skills/ticket-authoring "$out"/ticket-authoring &&(cd "$out" && zip -qr - ticket-authoring) > ticket-authoring.zip &&rm -rf "$tmp" "$out"

In Claude, open Customize > Skills, select +, then + Create skill > Upload a skill, and choose ticket-authoring.zip.

On Free, Pro and Max plans, turn on Code execution and file creation (Create and edit files in newer settings) under Settings > Capabilities.

Claude apps docs

Pinned to commit 9b90db2, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&mkdir -p .agents/skills &&mkdir .agents/skills/ticket-authoring &&cp -R "$tmp"/skills/ticket-authoring/. .agents/skills/ticket-authoring/ &&rm -rf "$tmp"

Codex picks up new skills on its own; restart it if this one does not appear.

Codex docs

Pinned to commit 9b90db2, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&mkdir -p .cursor/skills &&mkdir .cursor/skills/ticket-authoring &&cp -R "$tmp"/skills/ticket-authoring/. .cursor/skills/ticket-authoring/ &&rm -rf "$tmp"

Cursor docs

Pinned to commit 9b90db2, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&mkdir -p .github/skills &&mkdir .github/skills/ticket-authoring &&cp -R "$tmp"/skills/ticket-authoring/. .github/skills/ticket-authoring/ &&rm -rf "$tmp"

In a running Copilot CLI session, run /skills reload.

Or install it with gh skill, which also installs the commit we checked. Needs GitHub CLI 2.90 or later.

gh skill install rampstackco/claude-skills skills/ticket-authoring/SKILL.md@9b90db257f7395fab76ff9bfcb808456709f6af3 --agent github-copilot --scope project

Copilot & VS Code docs

Pinned to commit 9b90db2, the one we checked.

From your project's root folder:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&mkdir -p .gemini/skills &&mkdir .gemini/skills/ticket-authoring &&cp -R "$tmp"/skills/ticket-authoring/. .gemini/skills/ticket-authoring/ &&rm -rf "$tmp"

In a running session, run /skills reload.

Or use Gemini CLI’s own installer. Installs the latest version, not the one we checked.

gemini skills install https://github.com/rampstackco/claude-skills.git --path skills/ticket-authoring --scope workspace

Gemini CLI docs

Pinned to commit 9b90db2, the one we checked.

OpenCode, Goose, Windsurf (Devin Desktop), Zed, Roo Code, Factory Droid, Junie, Amp and Antigravity read .agents/skills in a project.

From your project's root folder:

tmp="$(mktemp -d)" &&git clone -q --depth 1 --filter=blob:none --no-checkout https://github.com/rampstackco/claude-skills.git "$tmp" &&git -C "$tmp" fetch -q --depth 1 origin 9b90db257f7395fab76ff9bfcb808456709f6af3 &&git -C "$tmp" sparse-checkout set -- skills/ticket-authoring &&git -C "$tmp" checkout -q 9b90db257f7395fab76ff9bfcb808456709f6af3 &&mkdir -p .agents/skills &&mkdir .agents/skills/ticket-authoring &&cp -R "$tmp"/skills/ticket-authoring/. .agents/skills/ticket-authoring/ &&rm -rf "$tmp"

Or use the skills CLI from skills.sh. Installs the latest version, not the one we checked. The skills CLI reports installs to skills.sh unless you set DISABLE_TELEMETRY=1.

npx skills@1.7.4 add rampstackco/claude-skills --skill ticket-authoring

Agent Skills docs

Read SKILL.md first

MIT

Licence

1.0k

Repo stars

Folder last changed

Publisher

Files

Checked

3 Nov 2026

What it can touch

From the files and frontmatter at commit 9b90db2. This is how much a skill can do, not whether it is risky.

Names web addresses
It mentions outside web addresses the agent may visit. We list them but don't follow them.
Outside links we did not follow

Pattern check

Pattern check: nothing flagged · commit 9b90db2 · 3 Nov 2026

We checked every text file in this skill, at commit 9b90db2 on 3 Nov 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check works Report an incorrect finding

Outside links we did not follow

https://openaddict.com/skills/coverage

Format check

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

Agent Skills specPasses with warnings
The open format from agentskills.io, held to the strictest version of each rule among the agents we check.
- Warning
  Fields outside the spec: category, catalog_summary and display_order. Uploads to the Claude apps and API, and the spec's validator, reject the file; most agents ignore these fields. O1
  Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.
- Note
  There is no license field, so readers can't tell whether they may reuse the skill. O2
  Fix: Add license: with an SPDX name such as MIT or Apache-2.0, or the name of a bundled licence file.
- Note
  Reference files over 100 lines with no table of contents at the top: references/bug-template.md (119 lines), references/capitalization-guide.md (113 lines) and references/example-bug-and-story.md (129 lines). B5
  Fix: Add a short list of the sections at the top of each.
Claude CodePasses
Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.
- Note
  Claude Code ignores fields it doesn't know: category, catalog_summary and display_order. O1
  Fix: Check the spelling against Claude Code's field list, or delete them.
- Note
  Reference files over 100 lines with no table of contents at the top: references/bug-template.md (119 lines), references/capitalization-guide.md (113 lines) and references/example-bug-and-story.md (129 lines). B5
  Fix: Add a short list of the sections at the top of each.
Claude apps & API uploadFails
Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.
- Error
  Upload and packaging fail on fields outside the spec: category, catalog_summary and display_order. O1
  Fix: Delete them, and keep your own data under metadata as text values.
- Note
  The description is 782 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4
  Fix: If the claude.ai upload refuses it, trim the description to 200 characters.
- Note
  Reference files over 100 lines with no table of contents at the top: references/bug-template.md (119 lines), references/capitalization-guide.md (113 lines) and references/example-bug-and-story.md (129 lines). B5
  Fix: Add a short list of the sections at the top of each.
OpenAI (Codex & API)Passes with warnings
Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.
- Warning
  Fields outside the spec: category, catalog_summary and display_order. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1
  Fix: Delete them, or move your own data under metadata as text values.
VS Code & CopilotPasses
VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.
- Note
  VS Code ignores fields it doesn't support: category, catalog_summary and display_order. O1
  Fix: Delete them unless another agent you target reads them.

SKILL.md

Read SKILL.md on GitHub

Files

10 files

Path	Size
README.md (opens in a new tab)	357 B
SKILL.md (opens in a new tab)	10.2 KB
references/bug-template.md (opens in a new tab)	3.9 KB
references/capitalization-guide.md (opens in a new tab)	5.8 KB
references/definition-of-ready-checklist.md (opens in a new tab)	3.3 KB
references/epic-template.md (opens in a new tab)	2.4 KB
references/example-bug-and-story.md (opens in a new tab)	5.8 KB
references/spike-template.md (opens in a new tab)	2.3 KB
references/story-template.md (opens in a new tab)	2.8 KB
references/task-template.md (opens in a new tab)	2.7 KB

More from rampstackco/claude-skills

Skill	What it can touch	Pattern check	Licence	Updated
accessibility-auditRun a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation. Names web addresses Pattern check: Nothing flaggedMITUpdated 4 Oct 2026	Names web addresses	Pattern check: Nothing flagged	MIT	4 Oct 2026
ads-creative-developmentHow to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting. Names web addresses Pattern check: Nothing flaggedMITUpdated 4 Oct 2026	Names web addresses	Pattern check: Nothing flagged	MIT	4 Oct 2026
ads-performance-analyticsHow to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue. Names web addresses Pattern check: Nothing flaggedMITUpdated 4 Oct 2026	Names web addresses	Pattern check: Nothing flagged	MIT	4 Oct 2026
after-action-reportRun a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings. Names web addresses Pattern check: Nothing flaggedMITUpdated 4 Oct 2026	Names web addresses	Pattern check: Nothing flagged	MIT	4 Oct 2026
ai-content-collaborationHow humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy. Names web addresses Pattern check: Nothing flaggedMITUpdated 4 Oct 2026	Names web addresses	Pattern check: Nothing flagged	MIT	4 Oct 2026
analytics-strategyDesign measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track. Names web addresses Pattern check: Nothing flaggedMITUpdated 4 Oct 2026	Names web addresses	Pattern check: Nothing flagged	MIT	4 Oct 2026

All skills in rampstackco/claude-skills

Other Product & project management skills

Same category, most repo stars first.

Skill	What it can touch	Pattern check	Licence	Updated
executing-plansUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available obra/superpowers Runs shell commands +1 more Pattern check: Nothing flaggedMITUpdated 21 Oct 2026	Runs shell commands Bundles scripts	Pattern check: Nothing flagged	MIT	21 Oct 2026
writing-plansUse when you have a spec or requirements for a multi-step task, before touching code obra/superpowers Instructions only Pattern check: Nothing flaggedMITUpdated 25 Sept 2026	Instructions only	Pattern check: Nothing flagged	MIT	25 Sept 2026
blueprintTurn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects: one-PR-sized steps with self-contained context briefs, dependency graph with parallel-step detection, adversarial review gate, and plan mutation protocol. Use when planning a large feature, refactor, or roadmap that spans multiple PRs or sessions; not for single-PR tasks or when the user says "just do it". affaan-m/ECC Changes agent settings +2 more Pattern check: Nothing flaggedMITUpdated 1 Oct 2026	Changes agent settings Runs shell commands +1 more	Pattern check: Nothing flagged	MIT	1 Oct 2026
brownfield-retrospectiveRun the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one. affaan-m/ECC Runs shell commands Pattern check: Nothing flaggedMITUpdated 10 Oct 2026	Runs shell commands	Pattern check: Nothing flagged	MIT	10 Oct 2026
discernment-nudgeAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. anthropics/skills Names web addresses Pattern check: Nothing flaggedApache 2.0Updated 17 Aug 2026	Names web addresses	Pattern check: Nothing flagged	Apache 2.0	17 Aug 2026
eval-planPreregister a paid eval (bars, arms, decoys, stop rules), dry-run it at zero cost, then run a three-item priced pilot whose spend table gates approval. (gstack) garrytan/gstack Runs shell commands +1 more Pattern check: 1 item to reviewMITUpdated 2 Nov 2026	Runs shell commands Pre-approves tools	Pattern check: 1 item to review	MIT	2 Nov 2026

At a glance

What it can touch

Pattern check

Install

Claude Code

Claude apps

Codex

Cursor

Copilot & VS Code

Gemini CLI

Any agent

What it can touch

Pattern check

Outside links we did not follow

Format check

SKILL.md

Files

More from rampstackco/claude-skills

Other Product & project management skills