Files

shokollm b3171ed632 feat(kugetsu): add status, delegate, doctor commands; inject PM context at init

This commit implements Phase 3b/3c architectural improvements:

### New kugetsu CLI commands:
- `kugetsu status` - Check initialization status (replaces kugetsu-helper check-status)
- `kugetsu delegate <msg>` - Send message to PM agent (new command)
- `kugetsu doctor [--fix]` - Diagnose and fix kugetsu issues

### PM Context Injection:
- kugetsu init now reads ~/.kugetsu/pm-agent.md (if exists) and injects
  it into the PM agent session at creation time
- PM context is loaded ONCE at init, not on every delegation
- This improves efficiency - kugetsu-pm content read once, not 10 times

### kugetsu-chat updated:
- Now uses `kugetsu delegate` instead of kugetsu-helper
- Now uses `kugetsu status` instead of kugetsu-helper check-status
- Simplified - no longer depends on kugetsu-helpers

### kugetsu continue:
- Removed strict issue-ref format validation
- Now accepts any session name that is tracked in index.json["issues"]
- Issue-ref format is a guideline, not a hard requirement

### Documentation updated:
- phase3a-setup.md - Updated to reflect new kugetsu commands
- kugetsu-install.sh - Simplified Phase 3a setup instructions

### Breaking changes:
- kugetsu-helpers is no longer required for Phase 3a Chat Agent
- kugetsu-chat skill v3.0 now requires kugetsu CLI with new commands

2026-03-31 01:09:12 +00:00

2.4 KiB

Raw Blame History

name, description, license, compatibility, metadata

name

description

license

compatibility

metadata

kugetsu-chat

Kugetsu Chat Agent - REQUIRED skill for ALL non-casual Telegram messages. This skill MUST be loaded and used for task delegation.

MIT

Requires Hermes agent with Telegram configured, kugetsu CLI, opencode sessions.

author	version
shoko	3.0

kugetsu-chat - REQUIRED SKILL FOR KUGETSU ROUTING

THIS SKILL MUST BE USED for any message that is not casual conversation.

CRITICAL: When to Use This Skill

YOU MUST LOAD AND USE THIS SKILL when:

Any message containing "issue", "fix", "create", "test", "implement"
Any message containing issue numbers like "#5", "#14", "#123"
Any message that looks like a task request or status query
Any message containing "pm", "status", "progress", "work on"

DO NOT USE THIS SKILL for:

"hi", "hello", "hey"
"thanks", "thank you"
"how are you", "what's up"
Casual greetings

Required Actions

When you MUST use this skill:

Step 1: Load This Skill

/kugetsu-chat

Step 2: Check if kugetsu is initialized

terminal(command="kugetsu status", timeout=10)

Step 3: If initialized, DELEGATE immediately

terminal(command="kugetsu delegate '<entire user message>'", timeout=120)

Step 4: Relay the response to the user

Delegation Command

The ONLY command you should use for delegation:

kugetsu delegate '<user message>'

Example:

terminal(command="kugetsu delegate 'fix issue #5 in github.com/shoko/kugetsu'", timeout=120)

Error Handling

Status Output	Meaning	Action
`ok`	kugetsu is ready	Proceed with delegation
`kugetsu_not_initialized`	Not set up	Tell user to run `kugetsu init`
`pm_agent_missing`	PM not created	Tell user to run `kugetsu init`
`pm_agent_expired`	PM session expired	Tell user to run `kugetsu doctor --fix`

Quick Reference

DELEGATION COMMAND:

terminal(command="kugetsu delegate '<message>'", timeout=120)

CHECK STATUS:

terminal(command="kugetsu status", timeout=10)

Required Dependencies

kugetsu CLI installed and in PATH
kugetsu initialized via kugetsu init

Notes

ALWAYS use kugetsu delegate command (not kugetsu-helper)
ALWAYS wrap user message in single quotes inside the command
ALWAYS use timeout of at least 120 seconds for delegation
kugetsu delegates to the persistent PM agent session created during init

2.4 KiB Raw Blame History