Review Vrau-generated brainstorm and plan documents for clarity and feasibility.
npx skills add https://github.com/mguilarducci/vrau --skill vrau-reviewer
Please help me install this Agent Skill. Skill: vrau-reviewer Source: https://github.com/mguilarducci/vrau/tree/main/skills/vrau-reviewer Command: npx skills add https://github.com/mguilarducci/vrau --skill vrau-reviewer
This Skill provides an unbiased, fresh perspective for reviewing brainstorm and plan documents generated by the Vrau workflow, ensuring quality and identifying potential issues before proceeding.
Use the vrau-reviewer skill to review the document at 'path/to/brainstorm.md'.
High-intent search queries and answers about installing and using this skill.
To review brainstorm and plan documents for completeness and feasibility, you can use an unbiased reviewer skill that evaluates clarity, dependency correctness, and task actionability, outputting a structured verdict with critical issues and suggestions.
The best way to check dependency correctness in a project plan is to use an automated document evaluation tool that assesses task actionability, commit points, and feasibility, calibrating its review depth based on the overall complexity of the tasks.
Yes, you can get objective feedback on a brainstorm document before planning by using a fresh-eyes reviewer approach that provides an unbiased perspective, ensuring document clarity and identifying potential issues before moving to the next phase.
Complexity calibration for document reviews works by adjusting the analysis depth based on task complexity, ranging from brief reviews for simple tasks to thorough and detailed analysis for highly complex project plans and brainstorms.
A structured review verdict for technical documents includes categorized feedback separated into critical issues that must be fixed, important issues to address, and optional suggestions for improving overall document quality and feasibility.
A limitation of automated plan document evaluation is that it relies strictly on the provided document content without prior context, meaning it may miss implicit project knowledge or unwritten team agreements not explicitly detailed in the brainstorm or plan text.
truongnatBreak down tasks, manage dependencies, and define acceptance criteria for execution plans.
FourthWizRevise implementation plans by addressing critic feedback and appending changelog entries.
CuriousCrow123Reviews brainstorm or plan documents for clarity, completeness, and actionability.
jey3dayoReview Markdown documentation for clarity, structure, and technical accuracy.
