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