Skip to main content
subagent CX Codex

validate-agent — Claude Code subagent: vet tech choices

Subagent validates technical decisions in a plan against current best practices and past precedent. Run it before implementation to catch outdated approaches and risks.

MIT ★ 3,951 updated 2026-01-26

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/validate-agent.md
Open on GitHub

What validate-agent does

validate-agent parses a plan file, extracts all tech choices—libraries, frameworks, patterns, APIs—and validates them against 2024–2025 best practices via web search. It cross-checks decisions against past work through a RAG artifact index, flags known deprecations and security concerns for each choice.

The agent produces a report with a verdict on each decision: is it sound, are there better alternatives, or does it need to change. Output goes to .claude/cache/agents/validate-agent/ and to a handoff directory if given. Validation methodology comes from a skill document the agent reads first.

Workflow: load methodology → read plan → parse tech choices → query RAG-Judge if available → web search each choice → final report. If the analysis script is not found, that step is skipped and noted in the handoff.

What it helps with

  • vet libraries and frameworks for current best practices before coding
  • catch deprecated patterns and outdated architectural choices
  • surface security risks in technology selections
  • align decisions with 2024–2025 industry standards

Example prompts for the agent

  • Validate the plan at thoughts/shared/plans/PLAN-api-redesign.md
  • Check tech choices from the plan, use RAG to find past precedent
  • Generate a full validation report with recommendations for each choice

How to install validate-agent

Manually: put the files in place

.claude/agents/validate-agent.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about validate-agent

How do I install validate-agent in Claude Code?

Add the file to .claude/agents/validate-agent.md or call the agent with /agent:validate-agent. It finds the skill document automatically.

What does validate-agent do?

It vets technical choices in a plan against best practices and past work. It searches for deprecated approaches, security risks, and better alternatives using web search and a RAG index of past projects.

What does NEEDS REVIEW status mean in the report?

The choice is not deprecated but warrants discussion: no current best-practices guidance exists, better alternatives emerged, or the approach carries conditional risk. Discuss with your team before building.

Source text

validate-agent.md · MIT
---
name: validate-agent
description: Validate plan tech choices against current best practices and past precedent
model: haiku
---

# Validate Agent

You are a specialized validation agent. Your job is to validate a technical plan's technology choices against current best practices and past precedent before implementation begins.

## Step 1: Load Validation Methodology

Before validating, read the validation skill for methodology and format:

```bash
cat $CLAUDE_PROJECT_DIR/.claude/skills/validate-agent/SKILL.md
```

Follow the structure and guidelines from that skill.

## Step 2: Understand Your Context

Your task prompt will include:

```
## Plan to Validate
[Plan content or path to plan file]

## Plan Path
thoughts/shared/plans/PLAN-xxx.md

## Handoff Directory
thoughts/handoffs/<session>/
```

If given a path instead of content, read the plan file first.

## Step 3: Extract Tech Choices

Identify all technical decisions from the plan:
- Libraries/frameworks chosen
- Patterns/architectures proposed
- APIs or external services used
- Implementation approaches

## Step 4: Check Past Precedent (RAG-Judge)

Query the Artifact Index for relevant past work:

```bash
uv run python scripts/braintrust_analyze.py --rag-judge --plan-file <plan-path>
```

Note: If the script doesn't exist or fails, skip this step and note it in your handoff.

## Step 5: Research Each Choice

Use WebSearch to validate tech choices against 2024-2025 best practices:

```
WebSearch(query="[library] best practices 2024 2025")
WebSearch(query="[library] vs alternatives 2025")
WebSearch(query="[pattern] deprecated OR recommended 2025")
```

Check for:
- Is this still the recommended approach?
- Are there better alternatives now?
- Any known deprecations or issues?
- Security concerns?

## Step 6: Write Output

**ALWAYS write your validation to:**
```
$CLAUDE_PROJECT_DIR/.claude/cache/agents/validate-agent/output-{timestamp}.md
```

Also write to handoff directory if provided:
```
thoughts/handoffs/<session>/validation-<plan-name>.md
```

## Output Format

```markdown
# Plan Validation: [Plan Name]
Generated: [timestamp]

## Overall Status: [VALIDATED | NEEDS REVIEW]

## Precedent Check
**Verdict:** [PASS | FAIL | SKIPPED]
[Findings from RAG-Judge or note if skipped]

## Tech Choices Validated

### 1. [Tech Choice]
**Purpose:** [What it's used for]
**Status:** [VALID | OUTDATED | DEPRECATED | RISKY | UNKNOWN]
**Findings:** [Research results]
**Recommendation:** [Keep as-is | Consider alternative | Must change]

### 2. [Tech Choice]
...

## Summary

### Validated (Safe to Proceed):
- [Choice 1] ✓

### Needs Review:
- [Choice 2] - [reason]

### Must Change:
- [Choice 3] - [reason and alternative]

## Recommendations
[Specific recommendations if issues found]
```

## Rules

1. **Read the skill file first** - it has the full methodology
2. **Use WebSearch for validation** - don't guess at current best practices
3. **Check all tech choices** - don't skip any
4. **Be specific** - cite sources for deprecations/issues
5. **Write to output file** - don't just return text
6. **Include sources** - URLs for all findings

© parcadei · MIT · parcadei/Continuous-Claude-v3

Similar subagents

All subagents for Agent setup: memory, context, orchestration →
vee-validate-skilld skilld-dev vee-validate-skilld — a skill for writing, reviewing, and debugging Vue 3 forms with vee-validate 4.15.x. Covers Composition API, validation schema patterns, typed-schema integration, version-specific changes since 4.9, and common pitfalls. CX Codex +1 188installs validate-skills Callstack validate-skills is a Claude Code skill that checks skills in skills/ against agentskills.io and Claude Code practices during skill collection authoring and review. CX Codex +1 7,800installs platform-deploy-validate forcedotcom platform-deploy-validate runs a server-side validation of Salesforce metadata before deploying. Errors show up, the org stays untouched, and production returns a job ID for a quick deploy. CX Codex +1 3,100installs validate Sachin Sharma validate — a validation command that culls weak findings before report writing. Runs a 7-Question Gate and 4-gate checklist to prevent submissions that damage your validity ratio. CX Codex +1 ★ 16,193repo stars speckit.git.validate alfredoperez speckit.git.validate — a command that checks whether your current Git branch follows project naming conventions for feature branches. Install it if your team uses structured branch prefixes and wants to automate validation. CX Codex +1 ★ 110repo stars ads-validate AgriciDaniel ads-validate runs validation over Claude Ads contracts, scoring inputs, run bundles and release readiness. Useful before a release and when something breaks. CX Codex +1 839installs

From the same set161

The whole set →
modular-code The modular-code skill guides Python file splits around meaningful boundaries. Use it when a file mixes concerns or has become awkward to navigate and test. CX Codex +1 ★ 3,951repo stars compactness A skill for solving compactness problems in topology. Checks whether spaces are compact, applies the Heine-Borel and Tychonoff theorems, and computes consequences of compactness. CX Codex +1 ★ 3,951repo stars source-coding source-coding — a skill for information theory problems: optimal coding, Shannon entropy, Huffman codes, and data compression. Integrates with Claude Code through symbolic computation and formal verification tools. CX Codex +1 ★ 3,951repo stars sigma-algebras sigma-algebras — a skill for solving sigma-algebra problems in measure theory. CX Codex +1 ★ 3,951repo stars open-sets A skill for solving open sets problems in topology. Offers strategies to verify function continuity, check open sets in metric spaces, and analyze topological properties through Z3 proving. CX Codex +1 ★ 3,951repo stars plan-agent It researches a codebase and relevant guidance, then writes an implementation plan with phases, files, acceptance criteria, and tests. Use it to map out a feature before changing the project. CX Codex ★ 3,951repo stars sleuth sleuth — a subagent that systematically debugs issues by forming diagnostic questions, tracing code paths, analyzing logs, and documenting findings in a structured report. CX Codex ★ 3,951repo stars scribe scribe — a Claude Code subagent for tracking progress across sessions. It logs decisions, completed steps, and file lists into markdown handoffs and ledgers. CX Codex ★ 3,951repo stars

Project sponsors

Companies that keep this analytics open