task-queue

To queue tasks for Claude Code, external systems append a formatted markdown section to tasks/queue.md. This enables automated routing and prioritization of work items from sources like Telegram, GitHub Actions, cron jobs, and event buses.

Writing a task to queue.md requires a Queued header with a timestamp, plus Source, Task, and Priority fields. Issue, Agent, and Context fields are optional additions for providing more specific workflow routing context.

Yes, you can trigger Claude Code workflows from a Telegram bot or GitHub Actions. These external sources append work items to tasks/queue.md, which are then picked up at session start or during a /sprint execution.

Claude Code processes queued tasks by reading the structured fields in tasks/queue.md at session start or during a /sprint. Users review, approve, and move prioritized work items to tasks/current.md for execution.

The best way to manage automated task prioritization in markdown is appending structured sections with Priority and Source fields to tasks/queue.md. This allows external event buses and cron jobs to route work items for Claude Code to pick up.

Task-queue requires no external dependencies or API integrations. It operates purely by appending formatted markdown sections to tasks/queue.md, relying on external systems to handle the file writing and triggering.