document-review

Assesses clarity, completeness, specificity, and YAGNI adherence of plan documents.

49|4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/gvkhosla/compound-engineering-pi --skill document-review-gvkhosla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-review
Source: https://github.com/gvkhosla/compound-engineering-pi/tree/main/plugins/compound-engineering/skills/document-review
Command: npx skills add https://github.com/gvkhosla/compound-engineering-pi --skill document-review-gvkhosla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of unclear, incomplete, or overly complex documents by providing a structured review process to identify and rectify critical issues before proceeding.

Core Features & Use Cases

  • Clarity Assessment: Identifies vague language, unstated assumptions, and unclear problem statements.
  • Completeness Check: Ensures all required sections are present and constraints are clearly defined.
  • Specificity Evaluation: Verifies that documents are concrete enough for the next actionable step.
  • Simplification: Removes unnecessary complexity and hypothetical features while preserving essential details.
  • Use Case: After a team brainstorms a new feature, this Skill can review the resulting document to ensure the problem statement is precise and the proposed solution is focused, preventing scope creep and wasted effort.

Quick Start

Review the document located at /docs/plans/new-feature-plan.md to identify areas for improvement.

Frequently Asked Questions about document-review

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

FAQPage Schema
How do I review a brainstorm document for clarity and scope creep?

Refine a brainstorm document by evaluating clarity, completeness, and specificity. This review identifies vague problem statements and applies YAGNI principles to remove hypothetical features, ensuring the plan remains focused and actionable.

What is the best way to check if a plan document is ready for the next workflow step?

Check a plan document by verifying that all required sections are present, constraints are clearly defined, and the content is concrete enough for the next actionable step. This ensures the document is specific enough to proceed successfully.

How do I simplify a complex planning document without losing essential details?

Simplify a complex document by applying a structured review to remove unnecessary complexity and hypothetical features. This ensures the content remains focused and actionable while preserving the essential details required for workflow progression.

Can I use this document review process for any type of planning document?

Apply this document review process to brainstorm or plan documents requiring critical evaluation before workflow progression. It targets documents needing quality assurance to ensure actionable insights and focused content.

Why does my feature plan document lack actionable insights during evaluation?

A feature plan lacks actionable insights when it contains vague language, unstated assumptions, or overly complex solutions. A structured document review identifies these specific issues and rectifies them to ensure the problem statement is precise.