ticket-authoring SKILL.md skillA
ticket-authoring from vandanaajaydubey111/great-pm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vandanaajaydubey111/great-pm/ticket-authoring@git:20260722.05296a5Pins git:20260722.05296a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vandanaajaydubey111/great-pm
- Path
skills/ticket-authoring/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260722.05296a5, committed Jul 22, 2026
- Size
- 3,163 bytes
- Repository stars
- 3
- License
- MIT
Playbook for change tickets — the format that makes a work item buildable and traceable; outcome title, why, scope, acceptance criteria, dependencies, evidence links. The upstream contract that pr-authoring's PR closes against.
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
# Ticket Authoring — playbook A ticket is the smallest contract in the chain. The full thread runs: **PRD story → ticket → PR → review → merge → deploy** Each link closes against the previous one: the ticket's acceptance criteria come from a PRD story, and the PR's acceptance-evidence table proves the ticket's criteria. A ticket that can't be traced backward to a PRD story or forward to a PR is an orphan — orphans become scope creep. ## 1. Required fields 1. **Title** — the outcome, not the activity. "Define product requirements and user journeys", never "Work on docs". 2. **Why** — the gap this closes, with a link to the upstream artifact (PRD story ID, strategy decision, Discover signal). 3. **What (scope of THIS ticket)** — the single deliverable and its boundaries. One deliverable per ticket. 4. **Out of scope** — explicitly, even when it feels obvious. 5. **Acceptance criteria** — yes/no checkable. These are the SAME criteria the closing PR must evidence, row for row. 6. **Dependencies** — what must land first (`bd dep`), and what this ticket blocks. A silent dependency is a future stall. …
Read the whole file at its exact version.
How to install
mdr add vandanaajaydubey111/great-pm/ticket-authoring@sha256:4acbf5a301afe6e2The line at the top of this page pins the label git:20260722.05296a5, 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_xwxogmukiis7olml)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 22, 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 (3163 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
vandanaajaydubey111/great-pm · 3 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xwxogmukiis7olml GET https://markdownregistry.com/api/v1/resolve?ref=vandanaajaydubey111/great-pm/ticket-authoring GET https://markdownregistry.com/api/v1/blob/4acbf5a301afe6e2ea2764ae0f4bdd00ebecac26864870f5d402d580eda1045d
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 vandanaajaydubey111/great-pm
Every file in vandanaajaydubey111/great-pm