document-review

Review brainstorm and plan documents for clarity, scope, and decision visibility.

Updated Mar 9, 2026

Search Tags:#workflow #planning #editing #clarity #review #brainstorm #document

Ready to run

npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill document-review-rafayelgardishyan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-review
Source: https://github.com/RafayelGardishyan/rafayels-marketplace/tree/main/plugins/rafayels-engineering/.opencode/skills/document-review
Command: npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill document-review-rafayelgardishyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm or plan documents often contain ambiguities, gaps, or inconsistent scope. This skill provides structured review to improve clarity and alignment before advancing in the workflow.

Core Features & Use Cases

Structured critique of documents to surface unclear language, missing sections, and untested assumptions.
Guidance for maintaining scope, identifying open questions, and ensuring decisions are traceable.
Use Case: refine a brainstorm brief to prepare a concrete plan for the next workflow step.

Quick Start

Provide the path to a brainstorm or plan document for review, or I will locate the most recent brainstorm/plan in docs/brainstorms/ or docs/plans/.

Frequently Asked Questions about document-review

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

FAQPage Schema

How do I refine a brainstorm document before moving to the next workflow step?▼

To refine a brainstorm document, provide its file path for structured critique. The skill reviews documents in docs/brainstorms/ or docs/plans/, automatically surfacing ambiguities, flagging scope creep, and outlining recommended in-line edits for clarity and completeness.

What is the best way to review a plan document for scope creep and untested assumptions?▼

Reviewing a plan document for scope creep requires evaluating decision traceability and open questions. This skill provides structured critique that flags potential scope creep, identifies untested assumptions, and ensures decisions are traceable before the workflow advances.

How do I check if my planning document has missing sections and lacks specificity?▼

Checking a planning document for missing sections involves evaluating it against criteria for clarity, completeness, and specificity. This skill operates on files in docs/plans/ to surface gaps, untested assumptions, and unclear language, guiding improvements for alignment.

Can I automatically locate the most recent brainstorm or plan document for review?▼

Yes, you can automatically locate the most recent brainstorm or plan document for review. If you do not provide a specific file path, the skill will locate the most recent document in the docs/brainstorms/ or docs/plans/ directories.

Does document review work without any external dependencies or components?▼

Yes, document review works without any external dependencies or components. The skill operates independently to analyze brainstorm and plan documents, relying solely on the document text provided in the specified directories to generate critique.

Why should I use a structured critique for editing brainstorms instead of manual review?▼

Using a structured critique for editing brainstorms ensures consistent evaluation of clarity, scope, and decision visibility. Manual review often misses untested assumptions or scope creep, whereas this skill systematically outlines recommended in-line edits to satisfy completeness criteria.