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

Feature - Dev-PM Agent Loop (Phase 3: PM Medium Context Check) #218

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

Summary

Phase 3 of Dev-PM Agent Loop - PM agent checks medium complexity context.

Background

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

Phase 1 and Phase 2 must be completed first.

Phase 3 Goal

When PM agent is consulted by dev, PM should check (in addition to Phase 2):

  • Related issues
  • Repository wider context
  • Cross-issue dependencies

Medium Context Check

What PM checks (beyond Phase 2):

  1. Related issues

    • Are there linked issues that this PR affects?
    • Does this PR close any issues?
    • Are there conflicting/duplicate PRs?

  2. Repository wider context

    • Does this PR affect other parts of the codebase?
    • Are there shared utilities/modifications?
    • Breaking changes?

  3. Cross-issue dependencies

    • Issues mentioned in PR that need updating
    • Issues that should be linked

PM Output:

  • Guidance via PR comment
  • Issues found that need addressing
  • Suggestions for dev

Dependencies

  • Phase 1: Dev asks PM mechanism
  • Phase 2: PM simple context check

Status

Blocked - depends on Phase 1 and Phase 2.

Related

  • Meta: #215 [META] Dev-PM Agent Loop
  • Phase 1: #216 (Dev Asks PM)
  • Phase 2: #217 (PM Simple Context Check)
  • Phase 4: #219 (PM Complex Final Check)
## Summary Phase 3 of Dev-PM Agent Loop - PM agent checks medium complexity context. ## Background Tracked by meta issue: #215 [META] Dev-PM Agent Loop Phase 1 and Phase 2 must be completed first. ## Phase 3 Goal When PM agent is consulted by dev, PM should check (in addition to Phase 2): - Related issues - Repository wider context - Cross-issue dependencies ## Medium Context Check ### What PM checks (beyond Phase 2): 1. **Related issues** - Are there linked issues that this PR affects? - Does this PR close any issues? - Are there conflicting/duplicate PRs? 2. **Repository wider context** - Does this PR affect other parts of the codebase? - Are there shared utilities/modifications? - Breaking changes? 3. **Cross-issue dependencies** - Issues mentioned in PR that need updating - Issues that should be linked ### PM Output: - Guidance via PR comment - Issues found that need addressing - Suggestions for dev ## Dependencies - Phase 1: Dev asks PM mechanism - Phase 2: PM simple context check ## Status Blocked - depends on Phase 1 and Phase 2. ## Related - Meta: #215 [META] Dev-PM Agent Loop - Phase 1: #216 (Dev Asks PM) - Phase 2: #217 (PM Simple Context Check) - Phase 4: #219 (PM Complex Final Check)
shoko added the blocked label 2026-04-07 14:18:31 +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#218
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?