القائمة
Read and update initiatives, including the legacy read/update initiative tools.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | initiatives |
| description | Read and update initiatives, including the legacy read/update initiative tools. |
| version | 0.1.0 |
| category | object |
| contextFilter | {"workspaceTypes":["neutral","ai-priorities","opportunity"]} |
| tools | [{"name":"initiatives_list","description":"List initiatives in the current workspace with status and maturity metadata.","inputSchema":{"type":"object","properties":{"folderId":{"type":"string","description":"Optional folder filter."},"status":{"type":"string","description":"Optional status filter."}}}},{"name":"read_initiative","description":"Read one initiative by id with its structured fields.","inputSchema":{"type":"object","properties":{"initiativeId":{"type":"string","description":"Initiative identifier."}},"required":["initiativeId"]}},{"name":"update_initiative","description":"Update editable initiative fields after caller approval and authorization.","inputSchema":{"type":"object","properties":{"initiativeId":{"type":"string"},"patch":{"type":"object","additionalProperties":true}},"required":["initiativeId","patch"]},"sideEffect":true,"requiresApproval":true}] |
The initiatives skill exposes workspace-scoped initiative object tools. It
keeps the legacy tool names read_initiative and update_initiative for the
current migration step while grouping them under the object skill metadata.
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.
