Claude-skill-registry loom-ticketing

Use loom ticket for ticket creation, status updates, deps, and notes.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/loom-ticketing" ~/.claude/skills/majiayu000-claude-skill-registry-loom-ticketing && rm -rf "$T"

manifest: skills/data/loom-ticketing/SKILL.md

Canonical commands

Initialize (creates

.tickets/

```
compound_ticket(argv=["init"])
```

Create:

compound_ticket(argv=["create", "Add foo support", "-p", "2", "-t", "task", "--tags", "foo,bar"])

List / view:

```
compound_ticket(argv=["list"])
```
```
compound_ticket(argv=["ready"])
```
```
compound_ticket(argv=["show", "<id>"])
```

Update:

compound_ticket(argv=["update", "<id>", "--status", "in_progress"])

compound_ticket(argv=["update", "<id>", "--status", "closed"])

Notes:

compound_ticket(argv=["add-note", "<id>", "Found X. Fixed by Y."])

Dependencies:

```
compound_ticket(argv=["dep", "<id>"])
```

compound_ticket(argv=["dep-add", "<id>", "<dep-id>"])

compound_ticket(argv=["dep-rm", "<id>", "<dep-id>"])

Best practices

One “epic” ticket per feature, with task tickets beneath.
Record decisions and gotchas as notes, not in your head.
Use deps to make sequencing explicit (and reviewable).

Manual notes

This section is preserved when the skill is updated. Put human notes, caveats, and exceptions here.