Agent skill
file-ticket
Use after brainstorming to create a ticket in the project tracker with full context from the design session
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/file-ticket
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?