b3171ed632
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
Kugetsu
Name background: Kugetsu (月掴, "grasping the moon") is derived from Jujutsu Kaisen's "Tokusa no Kage Boujutsu" (Shadow Art Style) — a technique that summons up to ten different creatures from the user's shadow. This project embodies the concept of one orchestrator managing multiple specialized agents working in parallel.
Overview
Kugetsu is an agent orchestration system that enables parallel task execution across multiple repositories. Inspired by the IT department metaphor:
- Human acts as executive, reviewing and approving
- PM (Project Manager) Agent coordinates and delegates tasks
- Coding Agents execute tasks autonomously on assigned issues
The core idea: instead of working through issues one-by-one, a PM spawns multiple coding agents in parallel — similar to Hermes running multiple tasks, but scaled to a full team workflow.
Why
When you have 10 issues, typically you work through them sequentially. With Kugetsu:
- PM prioritizes and splits tasks
- Coding agents work in parallel on their own branches
- PM reviews and merges to a release branch
- Human provides final approval to master/main
This means your focus shifts from doing to overseeing — reviewing PRs, not writing code.
Status
Phase 1: Research & PoC
Current focus: Documenting architecture and researching Hermes/OpenClaw capabilities for multi-agent parallelization.
Testing PR merge workflow.
Documentation
- Architecture — Full system design
- Research Index — All research topics
License
MIT