TL;DR — I've created agents. The orchestration has been challenging, but a whole lot of fun now that it is working. I'm building a SaaS/PaaS platform as a solo dev, so dev eats all my time and marketing / outreach always gets dropped. The challenge was keeping me, Claude Cowork, Claude Chat, Claude Code, and my agents on the same context. 1. I created a context.md file that lives on a Google Drive mirror on my local machine. Both during and at the end of each Cowork session, Cowork updates it — strategy, new DB table names, edge functions, anything needed to talk about the whole platform. 2. Claude Chat can't natively read md files in Drive, so I deployed the context file to the cloud with a token for authorized access, so Chat can fetch it when I start a new conversation on my phone. 3. I built two skills: an outreach agent (direct email to users) and a content agent (social media copy, blog posts, video scripts). At the end of each Cowork session, Cowork updates the context doc and Code pushes it to the cloud. When I start the next Cowork session, it's like getting a briefing from a Chief of Staff — recap, leftovers, backlog, and proposed work orders for the agents. 4. I review the proposed work orders and tell Cowork to create them. Work orders are written into the context.md file, which the agent skills can read. 5. I activate the skills; each agent reads the context doc, finds its work orders, produces output in assigned folders, updates status to complete, and notifies me in the same Cowork session for review. If approved, the agents schedule the content.
ソロSaaS創業者のオーケストレーション構成：Cowork・Chat・Code・エージェントで共有コンテキスト
ソロ開発者がCoworkを「参謀長」レイヤーとして運用：Google Drive上の単一の context.md を真実源とし、Cowork が outreach / content agent の2つのスキルに work order を発行、Chat（モバイル）と Code（リポジトリ）も同じファイルを参照
Solo founder building a SaaS/PaaS platform with Claude Cowork as control plane
シナリオ
ソロ開発者が Cowork、Chat（モバイル）、Code（リポジトリ）、複数のエージェントスキルを並行使用。痛み：それぞれが文脈のサイロで、人間＋全 Claude 面＋エージェントの同期が困難。結果、マーケティング／アウトリーチ業務が後回しに。
プロンプト
At the end of each working session, update context.md at /path/to/GoogleDriveMirror/ with: strategy changes, new database table names / edge functions, UX decisions, and any info needed to discuss the entire platform. When I start the next Cowork session, read context.md and brief me like a Chief of Staff would: last session recap, leftover items, backlog, and proposed work orders for my outreach and content agent skills. I'll review and tell you which work orders to commit; append approved ones to context.md so the agents can pick them up when I activate them.
期待される結果
参謀長風のオーケストレーション構成を構築： 1. **context.md**（Google Drive ローカルミラー）＝単一の真実源 2. **Cowork**：各セッションの途中と終了時に context.md を更新；次回セッション開始時に参謀長のようにブリーフィング（前回のまとめ・残件・バックログ・推奨 work order） 3. **Claude Code**：context.md をトークン付きクラウドエンドポイントに push し、Chat から取得可能に 4. **Claude Chat（モバイル）**：認証トークンで同じファイルを参照 5. **2つのスキル**（outreach / content agent）：context.md を読み → 自分の work order を見つけ → 指定フォルダに成果物を保存 → ステータスを complete に更新 → 同一 Cowork セッションでユーザーに通知 **効果：** Cowork を開くたびに参謀長ブリーフィング状態。マーケ／アウトリーチが滞らず、全エージェントが同じ真実源を共有。