shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

feat(kugetsu): add queue infrastructure for autonomous PM #89

Closed
shoko wants to merge 1 commits from feat/issue-49-queue-infrastructure into main
pull from: feat/issue-49-queue-infrastructure
merge into: shoko:main
Conversation 0 Commits 1 Files Changed 1 +115
shoko commented 2026-04-02 01:23:48 +02:00
Owner
Copy Link

Summary

Phase 1 implementation for #49 - Task Queue Architecture for Autonomous PM and Dev Agents.

Queue System

Priority tiers:

  • dev_followups (highest) - Dev completed, PM needs to review/follow-up
  • user_interrupts (medium) - User requested something mid-flight
  • background (lowest) - Passive discovery from sources

Commands

# List queue status
kugetsu queue list

# Add task to queue
kugetsu queue enqueue dev_followups "Fix login bug"
kugetsu queue enqueue user_interrupts "work on #20"
kugetsu queue enqueue background "Scan Gitea issues"

# Get next task (PM only)
kugetsu queue dequeue

# Clear queue
kugetsu queue clear

Files

  • ~/.kugetsu/queue.json - Queue storage
  • Priority-based dequeue: dev_followups > user_interrupts > background

Future Phases

Phase 2: PM polling loop (continuous queue processing)
Phase 3: Source integration (Gitea cron, notifications)

Part of #49

## Summary Phase 1 implementation for #49 - Task Queue Architecture for Autonomous PM and Dev Agents. ## Queue System Priority tiers: - `dev_followups` (highest) - Dev completed, PM needs to review/follow-up - `user_interrupts` (medium) - User requested something mid-flight - `background` (lowest) - Passive discovery from sources ## Commands ```bash # List queue status kugetsu queue list # Add task to queue kugetsu queue enqueue dev_followups "Fix login bug" kugetsu queue enqueue user_interrupts "work on #20" kugetsu queue enqueue background "Scan Gitea issues" # Get next task (PM only) kugetsu queue dequeue # Clear queue kugetsu queue clear ``` ## Files - `~/.kugetsu/queue.json` - Queue storage - Priority-based dequeue: dev_followups > user_interrupts > background ## Future Phases Phase 2: PM polling loop (continuous queue processing) Phase 3: Source integration (Gitea cron, notifications) Part of #49
shoko added 1 commit 2026-04-02 01:23:49 +02:00
feat(kugetsu): add queue infrastructure for autonomous PM 9171e41e33 
Add queue management system for task queue architecture (Phase 1):

- Add QUEUE_FILE and POLL_INTERVAL constants
- Add init_queue() to initialize queue.json if missing
- Add cmd_queue with subcommands:
  - list: Show queue status with counts per tier
  - enqueue <tier> <msg>: Add task to queue
  - dequeue [tier]: Remove and return next task (priority order)
  - clear: Clear all queued tasks

Queue tiers:
- dev_followups (highest priority)
- user_interrupts (medium)
- background (lowest)

This enables the autonomous queue-based architecture where PM agent
continuously polls the queue and assigns work to dev agents.

Part of #49
Related to #46 (verbosity control)
shoko closed this pull request 2026-04-02 02:57:48 +02:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#89
Delete Branch "feat/issue-49-queue-infrastructure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?