ワンクリックでManusで任意のスキルを実行

tmux-kanban-mesh

スター2

フォーク0

更新日2026年5月22日 12:51

Develop tmux-kanban's main session, agent mesh, subagent roles, scoped memory tree, a-mail, review/dispatcher helpers, and cross-session coordination model.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

0xD009

0xD009/tmux-kanban

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

tmux-kanban Mesh

Concepts

The project is evolving from a tmux monitor into a kanban-aware agent cockpit:

Main session: a fixed tmux session for a conductor agent, configured by main_agent.
Agent mesh: optional helper-agent scaffold configured by agent_mesh.
Roles: review-permission, review-advice, dispatcher, session-link, memory-summarizer.
Scopes: global -> host -> session -> window -> pane.
Memory tree: scoped summaries that agents can read from root to leaf.
A-mail: scoped messages between helper agents.

Key Files

internal/mesh/mesh.go: pure role/scope/memory/mail/spec model.
internal/config/config.go: main_agent and agent_mesh YAML config.
internal/debug/snapshot.go: config/runtime summary in snapshots.
cmd/tmux-kanban/tui.go: runtime commands such as :main ... and :mesh ....
config.example.yaml and README.md: user-facing examples.

Design Guardrails

Keep agent_mesh.enabled default-off until real runtime dispatch is deliberate.
Runtime TUI commands should mutate in-memory config only; do not write config.yaml unless the user asks for persistence.
Prefer pure data structures and tests before starting real Codex/Claude/Hermes subprocesses.
Do not hard-code a single agent. Config should allow codex, claude-code, and custom commands.
Subagent behavior should be scoped: a session helper should not accidentally act on unrelated hosts/sessions.

Useful Commands

:main start
:main codex
:main claude
:main host local
:main session tmux-kanban-main
:main command codex

:mesh status
:mesh on
:mesh default claude
:mesh shared off
:mesh policy review-advice agent claude
:mesh policy review-advice off
:mesh mail dir ~/.local/state/tmux-kanban/mail

Validation

Mesh changes should usually include pure tests in internal/mesh and command tests in cmd/tmux-kanban/main_test.go.

go test ./...
go build -o ./bin/tmux-kanban ./cmd/tmux-kanban

このリポジトリの他の Skills

同じリポジトリ

tmux-kanban-config

0xD009/tmux-kanban

Write, edit, or review tmux-kanban configuration. Use when changing config.yaml, config.example.yaml, internal/config defaults or YAML loading, runtime :set/:settings behavior, Hermes scoped settings, agent_mesh/main_agent config, snapshot config summaries, or config documentation/tests.

2026-05-222

tmux-kanban-dev

0xD009/tmux-kanban

Develop the local tmux-kanban Go project. Use when changing architecture, core state logic, CLI commands, config loading, debug snapshots, tests, or general code in this repository.

2026-05-222

tmux-kanban-snapshot-debug

0xD009/tmux-kanban

Diagnose tmux-kanban debug snapshots and status misclassification bugs. Use when Codex is asked to inspect a tmux-kanban snapshot, explain why an agent/session was marked idle/working/need review/done, compare snapshot state with live tmux panes, debug review queue or preview inconsistencies, or use snapshot descriptions to reproduce classification problems.

2026-05-222

tmux-kanban-ui

0xD009/tmux-kanban

Work on tmux-kanban's Bubble Tea TUI, including layout, preview panels, input/message boxes, keybindings, kanban/session/review views, agent activity, and terminal UX polish.

2026-05-222

dispatcher

0xD009/tmux-kanban

Convert advice into scoped tmux-kanban proposals without executing them.

2026-05-212

memory-summarizer

0xD009/tmux-kanban

Produce scoped memory summaries for tmux-kanban.

2026-05-212

tmux-kanban Mesh

Concepts

The project is evolving from a tmux monitor into a kanban-aware agent cockpit:

Main session: a fixed tmux session for a conductor agent, configured by main_agent.

Agent mesh: optional helper-agent scaffold configured by agent_mesh.

Roles: review-permission, review-advice, dispatcher, session-link, memory-summarizer.

Scopes: global -> host -> session -> window -> pane.

Memory tree: scoped summaries that agents can read from root to leaf.

A-mail: scoped messages between helper agents.

Key Files

internal/mesh/mesh.go: pure role/scope/memory/mail/spec model.

internal/config/config.go: main_agent and agent_mesh YAML config.

internal/debug/snapshot.go: config/runtime summary in snapshots.

cmd/tmux-kanban/tui.go: runtime commands such as :main ... and :mesh ....

config.example.yaml and README.md: user-facing examples.

Design Guardrails

Keep agent_mesh.enabled default-off until real runtime dispatch is deliberate.

Runtime TUI commands should mutate in-memory config only; do not write config.yaml unless the user asks for persistence.

Prefer pure data structures and tests before starting real Codex/Claude/Hermes subprocesses.

Do not hard-code a single agent. Config should allow codex, claude-code, and custom commands.

Subagent behavior should be scoped: a session helper should not accidentally act on unrelated hosts/sessions.

Useful Commands

:main start :main codex :main claude :main host local :main session tmux-kanban-main :main command codex :mesh status :mesh on :mesh default claude :mesh shared off :mesh policy review-advice agent claude :mesh policy review-advice off :mesh mail dir ~/.local/state/tmux-kanban/mail

Validation

Mesh changes should usually include pure tests in internal/mesh and command tests in cmd/tmux-kanban/main_test.go.

go test ./... go build -o ./bin/tmux-kanban ./cmd/tmux-kanban

name	tmux-kanban-mesh
description	Develop tmux-kanban's main session, agent mesh, subagent roles, scoped memory tree, a-mail, review/dispatcher helpers, and cross-session coordination model.