bc40c4f500
### Changes:
1. **Moved kugetsu-pm to skills/kugetsu/pm/SKILL.md**
- Simplified to 79 lines (under 100 line target)
- kugetsu v3.0 with essential PM role definition
- PM context injected at init/start/continue time
2. **Updated kugetsu_get_pm_context()**
- Now reads from ~/.kugetsu/pm-agent.md (user custom) first
- Falls back to skills/kugetsu/pm/SKILL.md (default)
3. **Updated kugetsu-chat v4.0**
- Added notification checking on status/update queries
- When user asks "status?", "any updates?", etc., check kugetsu notify list
- Hybrid approach: PM includes notifications + kugetsu-chat checks on status
4. **Removed old skills/kugetsu-pm/SKILL.md**
- Replaced by skills/kugetsu/pm/SKILL.md
### Structure:
skills/kugetsu/
├── SKILL.md
├── scripts/kugetsu
├── chat/ # future: kugetsu-chat could move here
│ ├── SKILL.md
│ └── SOUL.md
└── pm/
└── SKILL.md # PM role definition (v3.0)
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