Claude-native starter kit that bootstraps multi-agent team infrastructure for any project. Clone once, install as a global skill, run /kit-install in any project directory. Includes: - 3-tier profile system (minimal/standard/full: 3-12 agents) - 16 agent archetype templates with personality spectrum - 18 skill templates using domain-action naming convention - Stakeholder persona panel for workshops and PR reviews - SQLite ticketing DB with CLI tools (config-based DB paths) - Decision tracking, sprint lifecycle, workshop orchestration - Multi-git-host support (GitHub, Gitea, GitLab) - /kit-update skill for syncing with source repo evolution - Naming theme support for agent identity/flavor - Smoke tests for all three profile tiers Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.4 KiB
2.4 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)
db/connectors/ticket list [--status S] [--priority P] [--epic N] [--sprint N] [--assigned A] [--team T]
Create ticket
db/connectors/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
db/connectors/ticket status <id> <new_status>
db/connectors/ticket done <id> [<id> ...]
Statuses: backlog, ready, in_progress, review, done, cancelled
Assignment
db/connectors/ticket assign <id> <agent>
db/connectors/ticket unassign <id>
Team assignment
db/connectors/ticket team <id> <teams>
Teams are comma-separated, e.g. backend, frontend, backend,frontend.
Sprint management
db/connectors/ticket sprint [--active]
db/connectors/ticket sprint assign <id> <sprint_id>
For sprint-scoped operations (status overview, context dumps, lifecycle),
use the dedicated sprint CLI instead: db/connectors/sprint --help
Dependencies
db/connectors/ticket deps <id>
Search and browse
db/connectors/ticket search <keyword>
db/connectors/ticket epics [--status S]
db/connectors/ticket children <id>
db/connectors/ticket count [--status S]
Batch show
db/connectors/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