ワンクリックで
solutions
Read solution records attached to opportunity workspaces and initiatives.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Read solution records attached to opportunity workspaces and initiatives.
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 | solutions |
| description | Read solution records attached to opportunity workspaces and initiatives. |
| version | 0.1.0 |
| category | object |
| contextFilter | {"workspaceTypes":["neutral","ai-priorities","opportunity"]} |
| tools | [{"name":"solutions_list","description":"List solutions in the current workspace.","inputSchema":{"type":"object","properties":{}}},{"name":"solution_get","description":"Read one solution by id.","inputSchema":{"type":"object","properties":{"solutionId":{"type":"string"}},"required":["solutionId"]}}] |
The solutions skill exposes workspace-scoped solution object tools for
proposed approaches, technical solutions, and opportunity solution records.
Handlers are intentionally not bound until chat-service is rebound to
SkillsToolRegistry.