subagentplatforms

Meta-workspace for the opensubagents stack. Single-clone entry point to all 8 canonical repos plus the cross-cutting notes that don't belong inside any one of them.

What's here

.
├── manifest.json             machine-readable SHA-pinned snapshot of all 8 siblings
│                             (auto-generated by gh_init_repo; canonical source of
│                             truth for tooling that consumes this repo)
├── .gitmodules               wiring for the 8 sibling repos (for `git submodule`)
├── README.md                 this file
├── CLAUDE.md                 agent-level workspace guidance
├── VENDORED_FROM.md          third-party upstreams we read from
├── LICENSE                   MIT
├── notes/
│   ├── journal.md            chronological session journal (curated)
│   ├── architecture.md       cross-repo data flow + dependency graph
│   └── planned-skills.md     5 placeholders from subagentskills/marketplace.json,
│                             with sketches of what each should do
├── diagrams/
│   └── org-overview.html     interactive HTML diagram of all 8 repos + flows
└── submodules/               8 git submodules pinned to current main HEADs
                              (materialized in commit 45e6b2a7)

manifest.json is the machine-readable source-of-truth for which sibling sits at which SHA. The Sibling repos table below is the human-readable version of the same data — when you bump a submodule SHA, regenerate the table from manifest.json rather than editing both by hand.

Sibling repos (8)

Repo	Status @ commit	What it is
ts-bootstrap-mcp	db22b540	MCP plugin: 7 tools for scaffolding TS projects in cloud web sandboxes. Ships ts-bootstrap.skill in dist-skills/.
subagentskills	17557d5f	Agent Skills catalog. marketplace.json + skills/ts-bootstrap/. Five more skills listed as planned.
subagentarch	15228221	Canonical GraphQL ERD for the org. Interactive HTML at docs/01-erd-overview.html. Kimball star-schema warehouse DDL for AlloyDB / Postgres 17.8 at warehouse/alloydb-17.8/.
subagenttasks	ab329d2c	Zod-derived JSON Schema + types + fixtures + 4 outcome tests for the task data model.
subagenttaskmaster	6a9c632a	Rebranded npm pack of eyaltoledano/claude-task-master published as @opensubagents/task-master-ai.
subagentbriefs	b538d087	Brief authoring chassis. PRD + brief template + first brief + 323-page Hamster crawl reference under discovery/.
subagenthtml	58c305be	Private fork of anthropics/html-effectiveness — 20-file HTML gallery for the "HTML is unreasonably effective" pattern.
subagentlsp	fd99391f	Vendored microsoft/vscode/extensions/html-language-features/server — LSP wrapper for the HTML language service.

Plus the non-org-owned gh-pr-mcp worker (deployed at gh-pr-mcp.alex-e62.workers.dev) — used by every push from a sandbox session.

Clone the whole stack

git clone https://github.com/opensubagents/subagentplatforms.git
cd subagentplatforms

# First-time setup: materialize the 8 submodules (see submodules/README.md)
# After the operator has run `git submodule add ...` once, all subsequent
# clones can use:
git clone --recurse-submodules https://github.com/opensubagents/subagentplatforms.git

Once submodules are wired, git submodule update --remote fast-forwards every sibling to its main HEAD; plain git submodule update checks out each at the SHA pinned in this repo's last commit (reproducible snapshot).

Why this exists

Walking into the stack cold means cloning 8 repos in 8 commands, learning which one owns the data model vs the scaffolding vs the catalog vs the tasks vs the briefs. This repo is the table of contents and the snapshot manifest.

It is not:

• a monorepo (each sibling stays autonomous)
• a build system (no source code lives here)
• a release manifest (siblings publish independently)

It is:

• the single command that gives you everything: git clone --recurse-submodules ...
• the home for cross-cutting notes that would feel awkward in any one sibling
• the canonical answer to "what's the state of the org right now?"

Bootstrap-commit caveats

This repo was bootstrapped from a sandbox via the GitHub Contents API (single-file PUTs) because the worker token's /git/trees write access wasn't yet provisioned on a brand-new repo. As a side effect:

• The submodules/ directory was empty in the bootstrap commit because /git/trees write access hadn't propagated to this newly-created repo yet. Commit 45e6b2a7 materialized all 8 gitlinks directly via the Git Data API once access propagated; see submodules/README.md for the current pin table.
• There are no CI workflows; the meta-repo has no validation surface of its own. Sibling repos handle their own validation.
• File modes are all 100644; this repo ships no executables.

All three are one-time follow-ups, not ongoing constraints.

See also

• CLAUDE.md — guidance for coding agents working here
• VENDORED_FROM.md — third-party upstreams we read for reference
• notes/journal.md — chronological session history
• notes/architecture.md — how the 8 repos wire together
• notes/planned-skills.md — design sketches for the 5 placeholder skills in subagentskills
• diagrams/org-overview.html — interactive map of the 8 repos and their data flows

License

MIT — matches every sibling.