القائمة
Review initiative gate criteria for a maturity-stage transition in AI-priorities and opportunity workspaces.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | gate_review |
| description | Review initiative gate criteria for a maturity-stage transition in AI-priorities and opportunity workspaces. |
| version | 0.1.0 |
| category | analysis |
| contextFilter | {"workspaceTypes":["neutral","ai-priorities","opportunity"]} |
| tools | [{"name":"gate_review","description":"Review gate criteria for an initiative maturity-stage transition.","inputSchema":{"type":"object","properties":{"initiativeId":{"type":"string","description":"Initiative ID."},"targetStage":{"type":"string","description":"Target maturity stage (for example G0, G2, G5, or G7)."}},"required":["initiativeId","targetStage"]}}] |
The gate_review skill evaluates whether an initiative is ready to move to a
target maturity stage based on the configured workspace gate criteria. Use it
when a caller wants blockers, warnings, or readiness feedback before a stage
transition.
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.
