skill-system-tkt

Automate ticket lifecycle management by coordinating multi-agent workflows across roadmaps, bundles, and durable tickets. The engine enforces governance policies, persists state in YAML or DB backends, and handles intake, claim, update, block, and close operations.

Filesystem-backed ticket governance uses project-level .tkt files for local bundles, while database-backed governance uses durable tickets for session-level lifecycle. Both backends enforce policy through close gates, audit tickets, and branch-aware workflows.

Initialize a project with init-roadmap, create a bundle with create-bundle, add worker tickets with add, then drive the lifecycle through update, claim, and close operations as needed.

Yes, branch-aware workflow automation supports optional git work trees and review artifacts. The engine coordinates operations across filesystem-backed bundles and database-backed memories, enforcing policy throughout real-world workflows.

PostgreSQL and psycopg2 are required for database-backed durable ticket sessions. However, you can use the filesystem-backed .tkt backend for project-level bundles without a database dependency.

Multi-agent workflow governance requires audit tickets and close gates to enforce policy and maintain an auditable workflow engine. These mechanisms ensure that intake, claim, update, block, and close operations remain canonical across project roadmaps.