CoVe Isolated Mode PRD
Extend the existing Chain-of-Verification (CoVe) skill with a new "isolated mode" that implements true factored verification using Claude Code's Task tool to spawn isolated sub-agents. This addresses the limitation that standard mode cannot achieve true context isolation since the model can still "see" its initial answer when answering verification questions.
Overview
CoVe Isolated Mode PRD
Overview
Extend the existing Chain-of-Verification (CoVe) skill with a new "isolated mode" that implements true factored verification using Claude Code's Task tool to spawn isolated sub-agents. This addresses the limitation that standard mode cannot achieve true context isolation since the model can still "see" its initial answer when answering verification questions.
Problem Statement
The current CoVe implementation uses prompt-based isolation ("mental reset" instructions) which is best-effort only. Research shows that when a model can see its initial answer while verifying, it may unconsciously repeat the same hallucinations. True factored verification requires each verification question to be answered in complete isolation with zero context about the initial answer.
Goals
- Implement true factored verification using sub-agents that have no access to the initial answer
- Create a new
/cove-isolatedcommand separate from the existing/covecommand - Support sub-agent customization via flags (
--explore,--haiku,--agent=<name>) - Run verification sub-agents in parallel to minimize latency
- Gracefully handle sub-agent failures
Non-Goals
- Modifying the existing
/covestandard mode behavior - Auto-triggering isolated mode (user must explicitly choose it)
- Creating new MCP tools or external dependencies
Technical Requirements
New Files
.claude/skills/cove/cove-isolated.md- Isolated mode workflow.claude/commands/cove/cove-isolated.md- Isolated mode command
Modified Files
.claude/skills/cove/SKILL.md- Add documentation for both modes
Workflow
The isolated mode workflow:
- Step 1-2: Same as standard mode (generate initial answer, generate verification questions)
- Step 3: Spawn isolated sub-agents via Task tool
- Parse flags from arguments
- For each verification question, create a Task call with minimal prompt (question only)
- Run all sub-agents in parallel (single message with multiple Task calls)
- Collect responses
- Step 4: Reconcile and produce final answer with agent metadata
Flag Support
| Flag | Effect |
|---|---|
--explore | Use Explore sub-agent type |
--haiku | Use haiku model |
--agent=<name> | Use custom sub-agent type |
Flags can be combined and must appear before the question.
Sub-Agent Prompt Template
You are answering a factual question. Research thoroughly using available tools
before answering. Cite your sources.
Question: {verification_question}
Requirements:
1. Use WebSearch, context7, Read, or other tools to verify your answer
2. If you cannot find authoritative sources, state that clearly
3. Provide a concise, factual answer with source citations
4. Do NOT speculate - only report what you can verify
Error Handling
- Sub-agent timeout: Mark verification as "Inconclusive"
- Sub-agent failure: Fall back to standard mode for that question
- All sub-agents fail: Abort and suggest using
/coveinstead
Success Criteria
/cove-isolatedcommand is recognized and invokes the isolated workflow- Sub-agents receive only the verification question (no initial answer context)
- Sub-agents run in parallel
- Output includes agent metadata and source citations
- Flags are parsed correctly and affect sub-agent behavior
- Errors are handled gracefully without crashing
Design Documents
- Design specification:
docs/cove/design.md(Verification Modes section) - Implementation plan:
docs/cove/implementation.md(Tasks 6-9)