Project instructions for FirenzeClaw's kimi-session-orchestrator, covering its metadata, folder structure, build and run commands, conventions, and architecture principles. The supplied entry does not include the detailed instructions.
A skill for coordinating several Kimi assistant sessions from a project-manager perspective. It covers planning, assigning work, checking results, and organising longer-running work.
Use when PM starts from a one-line product or engineering idea and must turn it into a locked Loop Contract before loop-orchestrator execution, including /loop-contract-new requests.
A workflow for repeatedly planning, assigning, checking, fixing, and delivering development work. It supports implementation, verification, or a combination of both, with optional parallel work.
Use when retiring a task session and spawning a successor with full context transfer — PM detects attention decay (≥360K context, norm deviation, hallucinations, repeated work), completes a major milestone, or needs a fresh session for the next phase. Use when PM says "退役"、"接班"、"换session"、"新session继续"。Requires…
A troubleshooting skill that asks for concrete facts, then obtains an independent second analysis when a complex problem or bug investigation is stuck.
A skill that asks for an independent second view when a coding problem remains stuck or an architecture choice has no clear answer. It gathers project context and passes it to another agent for a broader review, with up to three rounds when suggestions are rejected.
MCP server "kimi-session-orchestrator" as configured in FirenzeClaw/kimi-session-orchestrator. Runs locally from the kimi-session-orchestrator npm package.