AgentSkillsCN

Kuroryuu Patterns

当用户咨询“Kuroryuu 启动引导”、“多智能体协同”、“领导者-工作者模式”、“Promise 协议”、“k_ 工具”、“会话启动”、“检查点保存”、“收件箱消息”、“RAG 搜索”、“Kuroryuu 是如何运作的”、“Kuroryuu 架构”等话题,或需要 Kuroryuu 多智能体编排模式与工作流方面的指导时,应使用此技能。

SKILL.md
--- frontmatter
name: Kuroryuu Patterns
description: This skill should be used when the user asks about "Kuroryuu bootstrap", "multi-agent coordination", "leader worker pattern", "promise protocol", "k_ tools", "session start", "checkpoint save", "inbox messages", "RAG search", "how does Kuroryuu work", "Kuroryuu architecture", or needs guidance on Kuroryuu multi-agent orchestration patterns and workflows.
version: 1.0.0

Kuroryuu Multi-Agent Orchestration Patterns

Kuroryuu is a multi-agent orchestration system enabling Claude Code instances to coordinate as leaders and workers. This skill provides comprehensive guidance on patterns, protocols, and common workflows.

Quick Reference Index

Bootstrap Questions

QuestionAnswer Location
How do I start a session?KURORYUU_BOOTSTRAP.md → Session Start section
What's the difference between leader/worker?KURORYUU_LEADER.md vs KURORYUU_WORKER.md
How do I become a leader?Run /k-leader or read KURORYUU_LEADER.md
How do I become a worker?Run /k-worker or read KURORYUU_WORKER.md
What's the PRD-first workflow?KURORYUU_LEADER.md → PRD-First Workflow section
How do I save my progress?Run /k-save or use k_checkpoint(action="save")
How do I restore a checkpoint?Run /k-load or use k_checkpoint(action="load")

MCP Tools Quick Reference

ToolPurposePrimary Actions
k_sessionSession lifecyclestart, status, end
k_checkpointState persistencesave, load, list
k_inboxMessage queuesend, list, read, claim, complete
k_ragSemantic searchsearch, index
k_memoryWorking memorywrite, read, list
k_ptyPTY control (all agents)spawn_cli, talk, send_line
k_filesFile operationsread, write, list

Architecture Documents

DocumentLocationPurpose
BootstrapKURORYUU_BOOTSTRAP.mdSession start procedure
Leader ProtocolKURORYUU_LEADER.mdLeader responsibilities
Worker ProtocolKURORYUU_WORKER.mdWorker responsibilities
LawsKURORYUU_LAWS.mdOperational rules
Laws IndexKURORYUU_LAWS_INDEX.mdQuick law lookup
ArchitectureDocs/Plans/LEADER_FOLLOWER_ARCHITECTURE.mdSystem design

Core Concepts

Role Hierarchy

code
HUMAN
  │ (asks questions, approves plans)
  ▼
LEADER (one per orchestration)
  │ (delegates tasks, asks humans)
  ▼
WORKERS (many)
  │ (execute tasks, report progress)

Key Principle: Workers NEVER ask humans directly. All human interaction flows through the leader.

Session Lifecycle

code
1. Agent starts → Read KURORYUU_BOOTSTRAP.md
2. Determine role → Read KURORYUU_LEADER.md or KURORYUU_WORKER.md
3. Call k_session(action="start") → Get session_id
4. Register with Gateway → POST /v1/agents/register
5. Work loop → Execute tasks based on role
6. Save checkpoint → k_checkpoint(action="save")
7. End session → k_session(action="end")

Promise Protocol

Workers communicate status to leaders using promise tags:

Promise TagMeaningLeader Action
<promise>DONE</promise>Task completeCheck if all done → finalize
<promise>PROGRESS:N%</promise>Partial progressWait for more iterations
<promise>BLOCKED:reason</promise>External blockerInvestigate, clarify
<promise>STUCK:reason</promise>Can't proceedSend hint via leader_nudge.md

Common Workflows

Starting a New Session

  1. Read bootstrap: KURORYUU_BOOTSTRAP.md
  2. Determine role (first agent = leader, others = workers)
  3. Start session:
    code
    k_session(action="start", process_id="claude_code", agent_type="claude")
    
  4. Register role:
    code
    POST http://127.0.0.1:8200/v1/agents/register
    { "role": "leader", "agent_id": "<session_agent_id>" }
    
  5. Confirm: KURORYUU-aware. Role: leader. Session: <id>. Ready.

Saving Work (Checkpoint)

  1. Gather context summary
  2. Save checkpoint:
    code
    k_checkpoint(
      action="save",
      name="session",
      payload={
        "description": "Work description",
        "context_summary": "What was accomplished"
      }
    )
    
  3. Optionally write worklog to Docs/worklogs/

Sending Tasks (Leader → Worker)

  1. Create task via inbox:
    code
    k_inbox(
      action="send",
      to="worker-1",
      subject="Implement feature X",
      body="Details of what to implement..."
    )
    
  2. Monitor for promise responses
  3. If worker stuck, send hint

Receiving Tasks (Worker)

  1. Poll inbox:
    code
    k_inbox(action="list", filter="to:me,status:new")
    
  2. Claim task:
    code
    k_inbox(action="claim", message_id="<id>")
    
  3. Execute task
  4. Report progress: <promise>PROGRESS:50%</promise>
  5. Complete:
    code
    k_inbox(action="complete", message_id="<id>")
    
  6. Report done: <promise>DONE</promise>

Searching Codebase (RAG)

  1. Query RAG index:
    code
    k_rag(action="search", query="authentication flow", top_k=5)
    
  2. Review results with source files and snippets
  3. Read relevant files for full context

Leader-Only Operations

These operations require leader role:

PTY Control

Spawn and control worker CLIs:

code
k_pty(action="spawn_cli", cli_provider="claude", role="worker")
k_pty(action="talk", session_id="<id>", command="Implement feature X")

Task Orchestration

Create and manage tasks:

code
POST /v1/orchestration/tasks { "title": "...", "subtasks": [...] }
POST /v1/orchestration/subtasks/<id>/hint { "hint": "Try approach X" }

Prompt Files Reference

Leader prompts in ai/prompts/leader/:

PromptPurpose
leader_prime.mdLoad context, check PRD
leader_plan_feature.mdCreate implementation plan
leader_breakdown.mdConvert plan to subtasks
leader_nudge.mdHelp stuck workers
leader_finalize.mdComplete task, trigger reviews
leader_escalate.mdEscalate to human
leader_pty_module.mdPTY control patterns

Worker prompts in ai/prompts/worker/:

PromptPurpose
worker_execute.mdExecute assigned task
worker_report.mdReport progress

Context Management

80% Threshold Rule

At 80% context usage (20% remaining):

  1. Check ai/context_check.png for context percentage
  2. Run /k-save immediately
  3. Consider ending session

Automatic Checkpoints

Save checkpoints:

  • Every ~50 tool calls
  • Before ending session
  • When switching major tasks
  • Before complex operations

Troubleshooting

MCP Tools Unavailable

  1. Check stack: .\run_all.ps1
  2. Verify MCP: claude mcp list
  3. Restart MCP server if needed

Gateway Unavailable

  1. Check Gateway: http://127.0.0.1:8200/health
  2. Start stack: .\run_all.ps1
  3. Use MCP tools directly as fallback

Session Lost

  1. List checkpoints: k_checkpoint(action="list")
  2. Load latest: k_checkpoint(action="load", checkpoint_id="latest")
  3. Resume from checkpoint context

Additional Resources

For detailed patterns and advanced techniques:

  • references/tool-patterns.md - Detailed MCP tool usage patterns
  • references/orchestration-patterns.md - Multi-agent coordination patterns

For working examples:

  • <PROJECT_ROOT>\.claude\agents\ - Agent definitions
  • <PROJECT_ROOT>\ai\prompts\ - Prompt templates
  • <PROJECT_ROOT>\apps\mcp_core\tools_*.py - MCP tool implementations