メニュー
Manage prototypes — settle and evict. Use when you need to register or remove prototypes from the runtime.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Deepractice/RoleX --skill prototype-managementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Manage individual lifecycle and knowledge injection. Use when you need to create, retire, restore, or permanently remove individuals, or when you need to inject principles and procedures into an individual.
Manage issues between individuals using IssueX. Use when you need to publish issues, comment, close, assign, or label issues for structured communication between AI individuals.
Manage organizations and positions — founding, chartering, membership, duties, requirements, appointments, and dissolution.
SOC 職業分類に基づく
SKILL.md を表示中
| name | prototype-management |
| description | Manage prototypes — settle and evict. Use when you need to register or remove prototypes from the runtime. |
Feature: Prototype Registry Register and unregister prototypes. A prototype is an instruction set (prototype.json + .feature files) that materializes roles, organizations, and positions in the runtime when settled.
Scenario: settle — execute a prototype into the world Given you have a ResourceX source (local path or locator) containing a prototype When you call use with !prototype.settle Then the prototype.json is loaded and all @filename references are resolved And each instruction is executed in order against the runtime And the prototype id and source are registered in the prototype registry And parameters are: """ locator: "!prototype.settle" args: source: "./prototypes/rolex"
# or by registry locator:
locator: "!prototype.settle"
args:
source: "deepractice/rolex"
"""
Scenario: evict — remove a prototype from the registry Given a prototype is no longer needed When you call use with !prototype.evict Then the id is removed from the prototype registry And runtime entities created by the prototype are NOT removed And parameters are: """ locator: "!prototype.evict" args: id: "rolex" """
Scenario: Settle is idempotent Given a prototype has already been settled When settle is called again with the same source Then existing entities are skipped (all ops check for duplicate ids) And the result is identical to the first settle
Scenario: Auto-born on activate Given a prototype is registered but no runtime individual exists When activate is called with the individual's id Then the individual is automatically born from the prototype