validate-agent

You can validate technical choices by researching proposed libraries, frameworks, and APIs against current best practices. This skill performs web research and analyzes past project precedents to identify outdated, deprecated, or risky technologies in your plan, generating a detailed handoff report for your team.

Tech stack risk assessment evaluates proposed libraries, frameworks, and patterns for outdated or deprecated status. You need this validation before starting a new feature implementation to ensure your chosen technologies are industry-recommended and secure for your current development cycle.

Yes, validating technical plans requires web search capabilities to research current best practices and access to an artifact index for RAG-judge functionality. These dependencies enable the analysis of past project precedents and the identification of risky technologies in your implementation plan.

You can check past project precedents for similar technical decisions using RAG-judge functionality. This skill queries an artifact index to analyze previous successes and failures, providing context on whether your proposed technologies have performed reliably in comparable scenarios.

The best way to identify outdated or deprecated libraries in a plan file is to run automated tech validation against the document. This skill analyzes proposed technologies in your plan file, cross-references them with current web research, and flags any risky or deprecated choices for review.

Automated code review for plan analysis is limited by its dependency on web search availability and artifact index access. Without these inputs, the RAG-judge functionality cannot perform precedent analysis, and validation depth relies entirely on the specificity of technologies detailed in your plan file.