jpmschweitzerandClaude Opus 4.6
b025fe8152
Remove the db/connectors → tooling/db/ symlink added in Sprint 21 (#274) and migrate all references to use tooling/db/ directly. - Delete tracked symlink from db/connectors - Remove duplicate db/connectors/* permission patterns from settings - Update project-structure.md to reflect removal - Move whatsinagame/static/db/connectors/ to whatsinagame/static/tooling/db/ - Update 20 whatsinagame template, skill, and test files - Update comment references in client/tests/test_anti_tedium.gd - Historical docs (old sprint briefings, changelog, discussions) left as-is Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
name, description, user-invocable, allowed-tools
| name | description | user-invocable | allowed-tools |
|---|---|---|---|
| ticket | Manage project tickets in the SQLite ticketing database. Use when the user says "ticket", "create a ticket", "show tickets", "sprint", or invokes /ticket. Wraps the ticket CLI for structured project management operations. | true | Bash, Read, Grep, Glob |
Ticket Skill
Manage the project ticketing database. Basic usage (ticket list, ticket show,
ticket sprint --active) and raw SQL wrappers are documented in CLAUDE.md.
This skill covers the full command reference.
Commands
List tickets (full flags)
tooling/db/ticket list [--status S] [--priority P] [--epic N] [--sprint N] [--assigned A] [--team T]
Create ticket
tooling/db/ticket create <type> <title> [--parent N] [--priority P] [--decision D] [--team T]
Types: initiative, epic, story, task, bug
Priorities: critical, high, medium, low
Update status
tooling/db/ticket status <id> <new_status>
tooling/db/ticket done <id> [<id> ...]
Statuses: backlog, ready, in_progress, review, done, cancelled
Assignment
tooling/db/ticket assign <id> <agent>
tooling/db/ticket unassign <id>
Team assignment
tooling/db/ticket team <id> <teams>
Teams are comma-separated, e.g. backend, frontend, backend,frontend.
Sprint management
tooling/db/ticket sprint [--active]
tooling/db/ticket sprint assign <id> <sprint_id>
For sprint-scoped operations (status overview, context dumps, lifecycle),
use the dedicated sprint CLI instead: tooling/db/sprint --help
Dependencies
tooling/db/ticket deps <id>
Search and browse
tooling/db/ticket search <keyword>
tooling/db/ticket epics [--status S]
tooling/db/ticket children <id>
tooling/db/ticket count [--status S]
Batch show
tooling/db/ticket show --brief <id> [<id>...]
Workflow
- Project Manager is the primary user of this skill
- Decisions from decisions/ domain files become initiatives
- Initiatives break into epics (major work areas)
- Epics break into stories (user-facing deliverables)
- Stories break into tasks (concrete work items assignable to agents)
- Sprints group tasks into time-boxed work periods
- Track history via
ticket_historytable for audit trail