agent-spec-reviewer

Reviews frontend specification documents for completeness, clarity, feasibility, and consistency.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aroido/vibesmith --skill agent-spec-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-spec-reviewer
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/agent-spec-reviewer
Command: npx skills add https://github.com/aroido/vibesmith --skill agent-spec-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill rigorously reviews frontend specification documents, identifying and flagging issues related to completeness, clarity, feasibility, and consistency to ensure high-quality technical documentation.

Core Features & Use Cases

  • Comprehensive Validation: Checks specs against 4 key criteria: Completeness, Clarity, Feasibility, and Consistency.
  • Graded Feedback: Provides Critical, Warning, and Suggestion ratings for identified issues.
  • Domain-Specific Checks: Includes checks tailored for VibeSmith's AI agent components and business context.
  • Use Case: Before a new feature is developed, submit its specification document to this agent to receive a detailed report on potential flaws, ensuring developers work from a robust and well-defined plan.

Quick Start

Use the agent-spec-reviewer skill to review the frontend specification document located at '/path/to/spec.md'.

Frequently Asked Questions about agent-spec-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a frontend specification document for completeness and feasibility?

Validating a frontend specification document involves checking it against completeness, clarity, feasibility, and consistency criteria to identify flaws and ensure developers work from a robust, well-defined plan.

What is the best way to ensure frontend specs are flawless before development?

Ensuring flawless frontend specs requires generating a structured report with critical, warning, and suggestion levels that provides actionable solutions and auto-approval criteria based on business context.

Can I validate my technical writing against specific business context and domain principles?

Yes, validating technical writing against business context and VibeSmith domain principles is supported. The review checks frontend specs for consistency with implementation details and AI agent component standards.

How do I get actionable feedback on issues found during a spec review?

You get actionable feedback by generating a structured report that grades issues into critical, warning, and suggestion levels, with each level providing specific solutions to fix frontend specification documentation.

Does frontend spec review work without additional dependencies?

Yes, frontend spec review works without additional dependencies. It independently evaluates specification documents and outputs graded feedback based on domain principles, business context, and implementation details.