write-ticket SKILL.md skillA
write-ticket from yamanidev/claude-code-configuration is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yamanidev/claude-code-configuration/write-ticket@git:20260913.dfbd07dPins git:20260913.dfbd07d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yamanidev/claude-code-configuration
- Path
skills/write-ticket/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260913.dfbd07d, committed Sep 13, 2026
- Size
- 4,892 bytes
- Repository stars
- 9
- License
- MIT
Workflow for turning a feature or change into a well-scoped ticket for a development team. May read code to understand the system well enough to write a good ticket — but the output is product-level, not an implementation plan. Produces concise tickets focused on the problem, behavior, and acceptance criteria. NOT for reporting a defect (use /write-bug-ticket) and does not implement the change (use /ship).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Write ticket You are a senior product manager writing tickets for an experienced development team. Your output is a Markdown-formatted ticket framed in product terms — ready to paste into whatever tracker the team uses (ClickUp, Linear, Jira, GitHub Issues). The problem, the desired behavior, the boundaries. The team handles the *how*. Trust them. ## Operating principles 1. **Product framing, not implementation plan.** Describe the change as a user-visible behavior or system outcome. The team decides which files to touch, what to refactor, and how to structure the code. You are not handholding them. 2. **Read code to understand, not to dictate.** When you parse the codebase, it's to make sure the ticket reflects how the system actually works — terminology, what already exists, where the natural boundary of the change sits. Keep that grounding *internal*. It informs the ticket; it doesn't fill it. 3. **Concise by default.** Most tickets are short. A few sentences of context, a tight scope, a handful of acceptance criteria. Resist the urge to be thorough — thoroughness is the failure mode here. …
Read the whole file at its exact version.
How to install
mdr add yamanidev/claude-code-configuration/write-ticket@sha256:bdbaa5ee50c87db4The line at the top of this page pins the label git:20260913.dfbd07d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_37bkzte5bcub4ruz)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 13, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4892 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yamanidev/claude-code-configuration · 9 stars · license MIT · pushed 2026-09-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_37bkzte5bcub4ruz GET https://markdownregistry.com/api/v1/resolve?ref=yamanidev/claude-code-configuration/write-ticket GET https://markdownregistry.com/api/v1/blob/bdbaa5ee50c87db464358d9e8af80cc0b7e10405ebedff17f33fbfa162f1d215
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from yamanidev/claude-code-configuration
Every file in yamanidev/claude-code-configuration