To Tickets

Name: To Tickets
Author: Kripu77

ASecurity

Use when breaking a plan into tracer-bullet GitHub issues with blocking edges.

7 stars
0 votes
0 copies
3 views
Added August 31, 2026

ai-agentsgit

Security analysis

A100/100

Scanned August 31, 2026

npx -y skills add Kripu77/software-factory --skill to-tickets --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of To Tickets?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kripu77-to-tickets/badge)](https://www.skillsdirectory.com/skills/kripu77-to-tickets)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: to-tickets
description: Use when breaking a plan into tracer-bullet GitHub issues with blocking edges.
---

# To tickets

Vertical slices, not layers. Each ticket is demoable. Each names what blocks it.

Open issues on the owning service. Label `ready-for-agent`. Quiz the human before publishing. Do not write local scratch ticket files.

## Issue body

## What to build
End-to-end behavior from the user's perspective.

## Acceptance criteria
- [ ] ...

## Blocked by
None, or links to blocking issues.

No stale file paths in the body.