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

Feature - Dev-PM Agent Loop (Phase 1: Dev Asks PM) #216

New Issue
Open
opened 2026-04-07 14:18:16 +02:00 by shoko · 0 comments
shoko commented 2026-04-07 14:18:16 +02:00
Owner
Copy Link

Summary

Phase 1 of Dev-PM Agent Loop - Enable dev agent to ask PM agent when hitting a question/blocker.

Background

Tracked by meta issue: #215 [META] Dev-PM Agent Loop

Phase 1 Goal

Dev agent should never stop at blockers without asking PM. When dev has a question or hits a blocker, it should ask PM (low latency, async).

Research Required

1. How should dev ask PM?

Options:

  • notify - use existing notification system (low latency)
  • delegate-to-pm - queue a task for PM agent
  • hybrid - notify for quick questions, delegate for complex ones

2. What triggers dev to ask PM?

When should dev ask PM instead of stopping?

  • Every PR creation decision?
  • Only when dev has a question/blocker?
  • Specific signal patterns?

3. PM consultation mechanism

  • Async - dev continues, PM picks up when ready
  • Not sync - to avoid spawning multiple PM agents

4. What does dev tell PM?

When asking PM, what information does PM need?

  • Current work state
  • The question/blocker
  • PR draft link (if exists)
  • Issue context

Open Questions

  1. How to implement low-latency communication?
  2. Should dev wait for PM acknowledgment or just continue?
  3. How to handle multiple dev agents asking PM simultaneously?
  4. What's the format for dev to PM communication?

Status

Blocked - needs research before implementation.

Related

  • Meta: #215 [META] Dev-PM Agent Loop
  • Phase 2: #216 (PM Simple Context Check)
  • Phase 3: #217 (PM Medium Context Check)
  • Phase 4: #218 (PM Complex Final Check)
## Summary Phase 1 of Dev-PM Agent Loop - Enable dev agent to ask PM agent when hitting a question/blocker. ## Background Tracked by meta issue: #215 [META] Dev-PM Agent Loop ## Phase 1 Goal Dev agent should **never stop at blockers without asking PM**. When dev has a question or hits a blocker, it should ask PM (low latency, async). ## Research Required ### 1. How should dev ask PM? Options: - **notify** - use existing notification system (low latency) - **delegate-to-pm** - queue a task for PM agent - **hybrid** - notify for quick questions, delegate for complex ones ### 2. What triggers dev to ask PM? When should dev ask PM instead of stopping? - Every PR creation decision? - Only when dev has a question/blocker? - Specific signal patterns? ### 3. PM consultation mechanism - **Async** - dev continues, PM picks up when ready - **Not sync** - to avoid spawning multiple PM agents ### 4. What does dev tell PM? When asking PM, what information does PM need? - Current work state - The question/blocker - PR draft link (if exists) - Issue context ## Open Questions 1. How to implement low-latency communication? 2. Should dev wait for PM acknowledgment or just continue? 3. How to handle multiple dev agents asking PM simultaneously? 4. What's the format for dev to PM communication? ## Status Blocked - needs research before implementation. ## Related - Meta: #215 [META] Dev-PM Agent Loop - Phase 2: #216 (PM Simple Context Check) - Phase 3: #217 (PM Medium Context Check) - Phase 4: #218 (PM Complex Final Check)
shoko added the blocked label 2026-04-07 14:18:16 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 blocked
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#216
Delete Branch "%!s()"

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?