Agent skill
loom-ticketing
Use loom ticket for ticket creation, status updates, deps, and notes.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/loom-ticketing
Metadata
Additional technical details for this skill
- tags
- tickets,workflow
- version
- 1
- created at
- 2026-01-27T17:03:09.731823+00:00
- updated at
- 2026-01-27T17:03:09.731823+00:00
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?