Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Entry point for the BDB Agent OS suite installed as a Claude Code plugin. Use to find out which of the 200+ AOS skills, the seven startcycle subagents, or the pipeline workflows apply to a task, and where their contracts live. Reach for a specific skill directly when you already know its name — this skill only routes.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The full AOS suite: 200+ skills, 29 subagents, and the startcycle pipelines.
| Component | Location |
|---|---|
| Skills | skills/<category>/<name>/SKILL.md |
| Subagents | agents/<name>.md (mirrors .claude/agents/) |
| Pipeline contract | .agents/graph.md, node registry in .agents/nodes.json |
| State schema | .agents/state.schema.json |
Three variants, differing only in how much machinery the task needs:
| Skill | Shape |
|---|---|
startcycle | Linear chain: Architect → TechLead → parallel build → Reviewer. |
startcycle-graph | Dispatcher graph: durable state.json, Reviewer repair loop, automated quality gate, human escalation. |
startcycle-graph-user | Throwaway 2–4 node fan-out, nothing persistent left behind. |
Agents never invoke each other. A dispatcher — the main session or the workflow script — decides every next step. Routing lives in the graph contract, never inside an agent's prompt.
design-ui-ux, engineering-method, media-eventtech, bdb-core, library,
engineering-hardware, business-ops. Pick the narrowest match; a library skill should never
be pulled for a task a domain skill already covers.
The harness contract for every skill — required frontmatter, attribution,
source: for derived work — is in AGENTS.md at the repo root.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。