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-core-workflow-aBuild a Cohere v2 RAG pipeline with asymmetric embeddings, retrieval, Rerank v4, grounded Chat, and citation validation. Use when implementing grounded question answering. Trigger with "Cohere RAG", "Cohere retrieval", or "Cohere citations".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: cohere-core-workflow-a description: >- Build a Cohere v2 RAG pipeline with asymmetric embeddings, retrieval, Rerank v4, grounded Chat, and citation validation. Use when implementing grounded question answering. Trigger with "Cohere RAG", "Cohere retrieval", or "Cohere citations". argument-hint: "[repository-path] [retrieval-backend]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore jeremy@intentsolutions.io license: MIT tags:
Create a measurable retrieval pipeline that separates indexing, query embedding, candidate retrieval, reranking, generation, and citation checks.
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.
input_type=search_document and user queries with input_type=search_query.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 |
|---|---|
| Dimension mismatch | Stop and rebuild or select the index matching its recorded model contract. |
| No candidates | Return a grounded no-answer result instead of unconstrained generation. |
| Invalid citation | Reject or flag the answer and retain the evidence bundle. |
| Context overflow | Reduce or rechunk evidence; v2 does not provide legacy prompt truncation. |
Use this compact handoff shape to keep the selected scope, validation evidence, and operational result reviewable.
Input:
query=approved-fixture; retrieve=40; rerank=8; require-citations=true
Expected handoff:
answer=grounded; citations=valid; selected-doc-ids=recorded; eval=pass