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

PM agent needs enhanced context for delegation and conversation modes #220

New Issue
Closed
opened 2026-04-07 14:20:32 +02:00 by shoko · 0 comments
shoko commented 2026-04-07 14:20:32 +02:00
Owner
Copy Link

Problem

The PM agent (pm/SKILL.md) lacks guidance on:

  1. When to use kugetsu continue vs kugetsu start
  2. When to answer directly (conversational mode) vs when to delegate (task mode)
  3. Tools with params and expected returns

Current State

pm/SKILL.md only covers kugetsu start:

  • "Use `kugetsu start //# ""
  • Does NOT mention kugetsu continue
  • Does NOT clarify when to answer directly vs delegate

Desired Behavior

PM agent should have clear guidance for:

Task Mode (delegate via cmd_start/cmd_continue):

  • "work on issue #81"
  • "close PR #42"
  • "create a PR for issue #91"
  • "merge issue #101"
  • Any specific action requiring code work

Conversation Mode (answer directly):

  • "show open issues"
  • "what is the current state of repo"
  • "hi"
  • "show me recent commits"
  • Questions that do not require code changes

Tools Documentation

The PM context should include:

kugetsu start

Usage: kugetsu start <issue-ref> <task description>
Params:
  - issue-ref: format instance/user/repo#number (e.g., github.com/shoko/kugetsu#81)
  - task description: What the agent should do
Returns: Creates new worktree and dev session, returns session ID
When: Use when no existing session/worktree for this issue

kugetsu continue

Usage: kugetsu continue <issue-ref> [message]
Params:
  - issue-ref: format instance/user/repo#number
  - message: Optional additional instructions
Returns: Continues existing session, returns session ID
When: Use when worktree/session already exists for this issue

Direct Answer

When the query is conversational (questions, status checks, etc.), answer directly without delegating.

Files to Modify

  • skills/kugetsu/pm/SKILL.md - Add tools documentation and mode guidance
  • ~/.kugetsu/pm-agent.md (user override) - Same if user has custom PM context

Related

  • Issue #209 - Partial issue ref extraction (related: PM needs to know how to delegate properly)
## Problem The PM agent (pm/SKILL.md) lacks guidance on: 1. When to use `kugetsu continue` vs `kugetsu start` 2. When to answer directly (conversational mode) vs when to delegate (task mode) 3. Tools with params and expected returns ## Current State pm/SKILL.md only covers `kugetsu start`: - "Use `kugetsu start <domain>/<user>/<repo>#<issue> <task description>"" - Does NOT mention `kugetsu continue` - Does NOT clarify when to answer directly vs delegate ## Desired Behavior PM agent should have clear guidance for: ### Task Mode (delegate via cmd_start/cmd_continue): - "work on issue #81" - "close PR #42" - "create a PR for issue #91" - "merge issue #101" - Any specific action requiring code work ### Conversation Mode (answer directly): - "show open issues" - "what is the current state of repo" - "hi" - "show me recent commits" - Questions that do not require code changes ### Tools Documentation The PM context should include: #### kugetsu start ``` Usage: kugetsu start <issue-ref> <task description> Params: - issue-ref: format instance/user/repo#number (e.g., github.com/shoko/kugetsu#81) - task description: What the agent should do Returns: Creates new worktree and dev session, returns session ID When: Use when no existing session/worktree for this issue ``` #### kugetsu continue ``` Usage: kugetsu continue <issue-ref> [message] Params: - issue-ref: format instance/user/repo#number - message: Optional additional instructions Returns: Continues existing session, returns session ID When: Use when worktree/session already exists for this issue ``` #### Direct Answer When the query is conversational (questions, status checks, etc.), answer directly without delegating. ## Files to Modify - skills/kugetsu/pm/SKILL.md - Add tools documentation and mode guidance - ~/.kugetsu/pm-agent.md (user override) - Same if user has custom PM context ## Related - Issue #209 - Partial issue ref extraction (related: PM needs to know how to delegate properly)
shoko closed this issue 2026-04-07 14:25:51 +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
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#220
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?