command-spec-review

Review frontend feature specification documents for completeness, clarity, and feasibility.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the comprehensive review of frontend feature specification documents, ensuring they meet quality standards, align with business context, and are technically feasible before development begins.

Core Features & Use Cases

  • Automated Spec Validation: Checks for completeness, clarity, and adherence to VibeSmith's domain and architectural principles.
  • Feasibility Assessment: Verifies technical requirements, API endpoint existence, and realistic implementation timelines.
  • Use Case: Before starting development on a new dashboard feature, run this Skill on its spec document to catch potential issues like missing user personas, unclear success criteria, or non-existent API endpoints, preventing costly rework later.

Quick Start

Use the command-spec-review skill to review the specification document located at docs/frontend-specs/v1.1.0/features/dashboard.md.

Frequently Asked Questions about command-spec-review

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

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

To validate a feature specification, check its completeness, clarity, and adherence to architectural guidelines by cross-referencing user research, MoSCoW prioritization, and API contracts to produce structured feedback on critical issues and warnings.

What is automated spec validation and how does it catch missing requirements?

Automated spec validation assesses specification documents against domain guidelines and business context to detect missing user personas, unclear success criteria, and non-existent API endpoints before development begins.

How do I assess technical feasibility before starting frontend development?

Assess technical feasibility by verifying technical requirements, confirming API endpoint existence, and evaluating realistic implementation timelines directly against the feature specification document.

Can I use a spec review tool to check MoSCoW prioritization and API contracts?

Yes, feature spec review validates MoSCoW prioritization and API contracts within the specification document to ensure technical requirements and business context align before development starts.

What are the limitations of automated code review for feature specifications?

Automated spec review is limited by the provided specification document's content and cannot validate undocumented external dependencies or infer business logic beyond the stated API contracts.

When do I need to run a specification review for frontend features?

Run a specification review before starting development on new frontend features to catch missing user personas or unclear success criteria early, preventing costly rework later.