ticket-pack-builder

To create a repo-local ticket system, the Skill generates a machine-readable manifest, a human-readable board, and per-ticket files. This structures work into a backlog that autonomous agents can follow without re-planning the entire project.

Scaffolding a ticket backlog generates specific files: tickets/manifest.json for machine-readable tracking, BOARD.md for human-readable oversight, individual tickets/*.md files, and integration with .opencode/state/workflow-state.json.

Yes, you can retrofit an existing repository with a structured ticket board. The Skill supports retrofit backlog maintenance and post-audit repair workflows, decomposing existing work into a clear, ticket-driven plan for OpenCode-style repos.

Yes, the backlog generation tool integrates with OpenCode workflow state. It aligns with OpenCode-style projects and outputs state updates to .opencode/state/workflow-state.json to coordinate autonomous agents.

The best way to organize project tickets without re-planning is using a self-contained, repo-local ticket system. It outputs a structured manifest and per-ticket markdown files, allowing agents to execute work sequentially without re-evaluating the entire project scope.

Use a repo-local ticket manifest during greenfield scaffolding, retrofit backlog maintenance, or post-audit repair workflows. It provides a self-contained backlog directly in the repository, ensuring agents follow a structured plan without external dependencies.