القائمة
Create new Bedlam plugins with the current alpha SDK/runtime. Use when scaffolding a plugin package, adding a new example plugin, or updating plugin authoring docs. Covers the supported worker/UI surface, route conventions, scaffold flow, and verification steps.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Bedlam.
Technical guide for creating a new Bedlam agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.
Generate the stable Bedlam release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.
Coordinate a full Bedlam release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.
Interact with the Bedlam control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, or call any Bedlam API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Bedlam coordination.
| name | bedlam-create-plugin |
| description | Create new Bedlam plugins with the current alpha SDK/runtime. Use when scaffolding a plugin package, adding a new example plugin, or updating plugin authoring docs. Covers the supported worker/UI surface, route conventions, scaffold flow, and verification steps. |
Use this skill when the task is to create, scaffold, or document a Bedlam plugin.
Read these first when needed:
doc/plugins/PLUGIN_AUTHORING_GUIDE.mdpackages/plugins/sdk/README.mddoc/plugins/PLUGIN_SPEC.md only for future-looking contextCurrent runtime assumptions:
ctx.assets is not supported in the current runtimeUse the scaffold package instead of hand-writing the boilerplate:
pnpm --filter @bedlam/create-bedlam-plugin build
node packages/plugins/create-bedlam-plugin/dist/index.js <npm-package-name> --output <target-dir>
For a plugin that lives outside the Bedlam repo, pass --sdk-path and let the scaffold snapshot the local SDK/shared packages into .bedlam-sdk/:
pnpm --filter @bedlam/create-bedlam-plugin build
node packages/plugins/create-bedlam-plugin/dist/index.js @acme/plugin-name \
--output /absolute/path/to/plugin-repos \
--sdk-path /absolute/path/to/bedlam/packages/plugins/sdk
Recommended target inside this repo:
packages/plugins/examples/ for example pluginspackages/plugins/<name>/ folder if it is becoming a real packageCheck and adjust:
src/manifest.tssrc/worker.tssrc/ui/index.tsxtests/plugin.spec.tspackage.jsonMake sure the plugin:
ctx.assetsroutePath only on page slotsFor bundled example/discoverable behavior, update the relevant host wiring:
server/src/routes/plugins.tsOnly do this if the user wants the plugin surfaced as a bundled example.
Always run:
pnpm --filter <plugin-package> typecheck
pnpm --filter <plugin-package> test
pnpm --filter <plugin-package> build
If you changed SDK/host/plugin runtime code too, also run broader repo checks as appropriate.
When authoring or updating plugin docs: