executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cohere-sdk-patternsImplement a typed Cohere v2 provider boundary with timeouts, bounded retries, streaming, and response validation. Use when standardizing production SDK usage. Trigger with "Cohere SDK patterns", "Cohere client wrapper", or "refactor Cohere client".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: cohere-sdk-patterns description: >- Implement a typed Cohere v2 provider boundary with timeouts, bounded retries, streaming, and response validation. Use when standardizing production SDK usage. Trigger with "Cohere SDK patterns", "Cohere client wrapper", or "refactor Cohere client". argument-hint: "[repository-path] [typescript|python]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore jeremy@intentsolutions.io license: MIT tags:
Wrap generated SDK clients behind a small application contract so model changes, provider errors, and migrations stay localized.
Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content.
429, and eligible 5xx failures with jitter and a total-attempt ceiling.Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place CO_API_KEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions.
Do not expose or rotate keys, change Cohere Team roles, accept commercial terms, enable sensitive production data, increase spend or capacity, switch production models, send a support bundle, or execute model-proposed side effects without the accountable owner's approval. Keep diagnosis read-only unless implementation was requested.
Return the resolved API and model contract, files or settings inspected, evidence collected, validation result, remaining risk, owner, and rollback or next action. Redact keys, authorization headers, prompts, retrieved documents, embeddings, customer identifiers, and unrestricted environment output.
| Condition | Response |
|---|---|
| Unknown event | Preserve it in diagnostics and fail the affected stream safely. |
| Retry storm | Enforce jitter, an attempt ceiling, and a shared concurrency budget. |
| Type drift | Update the adapter against the pinned SDK and add a fixture. |
| Empty content | Treat it as an invalid result unless the operation expected tool calls. |
Use this compact handoff shape to keep the selected scope, validation evidence, and operational result reviewable.
Input:
operations=chat,embed,rerank; timeout=15s; retries=2; stream-cancel=true
Expected handoff:
adapter=typed; direct-sdk-calls=0; fixtures=pass; retry-budget=bounded