القائمة
Read and update folder matrix configurations in AI-priorities and opportunity workspaces.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | matrix |
| description | Read and update folder matrix configurations in AI-priorities and opportunity workspaces. |
| version | 0.1.0 |
| category | analysis |
| contextFilter | {"workspaceTypes":["neutral","ai-priorities","opportunity"]} |
| tools | [{"name":"matrix_get","description":"Read the matrix configuration (folders.matrixConfig) for a folder.","inputSchema":{"type":"object","properties":{"folderId":{"type":"string","description":"Folder ID owning the matrix configuration."}},"required":["folderId"]}},{"name":"matrix_update","description":"Update the matrix configuration for a folder after explicit caller approval.","inputSchema":{"type":"object","properties":{"folderId":{"type":"string","description":"Folder ID owning the matrix configuration."},"matrixConfig":{"type":"object","description":"New matrix configuration object.","additionalProperties":true}},"required":["folderId","matrixConfig"]},"sideEffect":true,"requiresApproval":true}] |
The matrix skill exposes the folder-level scoring and evaluation matrix used
by initiative and opportunity workflows. Use it when the user needs to inspect
or revise axes, thresholds, weights, or other matrix configuration fields.
Handlers are intentionally not bound in this package commit. Runtime execution
still routes through the legacy API tool service until BR-19 Lot 5 rebinds
chat-service to SkillsToolRegistry.
Use when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.
Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.
Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.
Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.
Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.
Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.
