Review frontend specification documents against a completeness and consistency checklist.
npx skills add https://github.com/aroido/vibesmith --skill spec-reviewer-aroido
Please help me install this Agent Skill. Skill: spec-reviewer Source: https://github.com/aroido/vibesmith/tree/main/.cursor/skills/spec-reviewer Command: npx skills add https://github.com/aroido/vibesmith --skill spec-reviewer-aroido
This Skill automates the review of frontend specification documents, ensuring they meet rigorous standards for completeness, clarity, feasibility, and consistency, thereby improving the quality and efficiency of the development process.
Use the spec-reviewer skill to review the attached document 'new-feature-spec.md'.
High-intent search queries and answers about installing and using this skill.
Reviewing a frontend specification document for completeness and clarity involves checking it against a detailed checklist covering business context, MoSCoW prioritization, feasibility, and architectural principles to generate structured feedback with critical issues and warnings.
MoSCoW prioritization in specification review validates whether requirements are categorized into Must-have, Should-have, Could-have, and Won't-have buckets, ensuring development feasibility and business context alignment before implementation begins.
Yes, automating quality assurance checks for frontend development specs uses a structured checklist to validate domain adherence and consistency, outputting standardized feedback identifying critical issues, warnings, and suggestions before human review.
Spec review requires predefined architectural principles and domain context to validate adherence. Without these structural baselines, the checklist cannot effectively assess feasibility, consistency, or business context alignment within the specification document.
The best way to structure specification review feedback is categorizing findings into Critical Issues, Warnings, and Suggestions, providing standardized, actionable insights that flag potential problems before development begins.
You need to run a specification review checklist when a new feature specification document is drafted, ensuring it meets completeness, clarity, and feasibility standards before progressing to human review or development implementation.
aroidoReview frontend feature specification documents for completeness, clarity, and feasibility.
FourthWizRevise implementation plans by addressing critic feedback and appending changelog entries.
k1lgorTranslate vague ideas into product plans with user stories and acceptance criteria.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
