To Tickets
Break a plan, spec, or conversation into tracer-bullet tickets with blocking edges, then publish them as Obsidian Issues.
Install
$ agentstack add skill-jesse-merhi-skills-to-tickets ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jesse-merhi-skills-to-tickets) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
To Tickets
Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it. Publish tickets to Obsidian Issues/.
Workflow
- Gather context from whatever is already in the conversation. If the user
passes a spec path or Obsidian note, fetch it and read the full body.
- Explore the codebase if needed. Ticket titles and descriptions should use
the project's glossary vocabulary and respect ADRs or Obsidian decisions in the area you are touching.
- Look for opportunities to prefactor the code to make implementation easier:
make the change easy, then make the easy change.
- Draft tracer-bullet tickets using [ticket-design.md](references/ticket-design.md).
Give each ticket its blocking edges. A ticket with no blockers can start immediately.
- Mark each ticket
AFKorHITL. - Present the proposed breakdown as a numbered list. For each ticket, show:
title, blocked by, mode, what it delivers, covered acceptance criteria, and any frontend validation state/viewport.
- Ask the user whether the granularity feels right, whether the blocking edges
are correct, and whether any tickets should be merged or split.
- Iterate until the user approves the breakdown.
- Publish the approved tickets to Obsidian
Issues/using
[note-template.md](references/note-template.md) and [naming.md](references/naming.md). If write access is missing, return the Markdown bodies and proposed paths.
- Do not close or modify any parent spec unless the user explicitly asks.
Context Pointers
- Use [ticket-design.md](references/ticket-design.md) for tracer-bullet rules,
wide refactors, and blocker checks.
- Use [execution-contract.md](references/execution-contract.md) for the ordered
todo contract.
- Use [note-template.md](references/note-template.md) for the ticket note body.
- Use [naming.md](references/naming.md) for vault-relative note paths.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jesse-merhi
- Source: jesse-merhi/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.