Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

file-ticket | dodi-dev

Home
Skills
dodi-dev
file-ticket

Skill

file-ticket

From dodi-dev

Use after brainstorming to create a ticket in the project tracker with full context from the design session

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/dodi-dev:file-ticket

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Create a ticket in the project tracker with context from the brainstorm/design session.

SKILL.md

36 lines · ~291 tokens

Stats

Parent stars0

MaintenanceExcellent

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Parent stars0

MaintenanceExcellent

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

File Ticket

Create a ticket in the project tracker with context from the brainstorm/design session.

Process

Gather from the session:
- Title — concise, action-oriented
- Description — what needs to be built and why
- Spec reference — path to the design spec (if written)
- Priority — infer from context (default: normal)
- Type — feature, bugfix, refactor
Create the ticket using available tools (Linear MCP, GitHub Issues, etc.)
Confirm with the user — show ticket ID and title

Ticket Content

The ticket description should include:

Summary of what was decided during brainstorming
Link/path to the design spec
Key constraints or decisions worth highlighting
NOT the full spec (that lives in the spec file)

Notes

This skill is tracker-agnostic — use whatever MCP tools are available
If no tracker tools are available, output the ticket content for the user to create manually
The ticket ID becomes the branch name in dodi-dev:pickup

$

npx claudepluginhub dodi-hq/dodi-skills --plugin dodi-dev

Similar Skills

ticket

15

Creates well-written tickets for your team's tracker (Linear, GitHub, Jira) by interviewing the user and routing to the appropriate pack.

ticket-writer

17

Interactively writes structured tickets (story, bug, epic, initiative, subtask, issue) with type-specific fields and quality checks. Outputs clean Markdown ready for any tracker.

6 files

playbooks-virtuoso

View ticket-writer

ticket-writer

23

Writes high-quality product tickets including user stories, bugs, improvements, spikes, and technical debt for Jira, Linear, Notion, GitHub Issues, or Markdown. Use to create, refine, split, or review tickets.

View ticket-writer