reporting-doc-reviewer

Review design and analysis reports for purpose, evidence, and conclusions.

5|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/xpgcrx/dotfiles --skill reporting-doc-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reporting-doc-reviewer
Source: https://github.com/xpgcrx/dotfiles/tree/main/gemini/skills/reporting-doc-reviewer
Command: npx skills add https://github.com/xpgcrx/dotfiles --skill reporting-doc-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewers need a clear, structured guide to evaluate and improve reporting documents such as design content and analysis results before sharing with stakeholders.

Core Features & Use Cases

  • Provides a standardized review checklist covering purpose, audience, evidence, and conclusions.
  • Offers guidance on how to structure feedback, prioritize issues, and propose concrete improvements.
  • Use Case: A product team shares a design document; this guide helps a reviewer assess clarity, alignment with goals, and risk.

Quick Start

Read a reporting document, identify gaps in purpose, evidence, and conclusions, then apply recommended edits to improve clarity and impact.

Frequently Asked Questions about reporting-doc-reviewer

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

FAQPage Schema
How do I review a design document before sharing it with stakeholders?

To review a design document, assess clarity, goal alignment, and risk using a standardized checklist covering purpose, audience, evidence, and conclusions to guide concrete improvements before sharing.

What should I look for when reviewing analysis reports?

When reviewing analysis reports, identify gaps in stated purpose, supporting evidence, and conclusions, then apply recommended edits to improve overall clarity and impact for stakeholders.

What is the best way to structure feedback on a product design document?

The best way to structure feedback on a product design document is to follow a structured review guide that helps prioritize identified issues and propose concrete improvements for cross-functional teams.

Can I use a structured review guide for cross-functional team reports?

Yes, you can use a structured review guide for cross-functional team reports in product, design, engineering, and research scenarios to evaluate reporting documents against standardized criteria.

How do I evaluate whether an analysis report has sufficient evidence?

Evaluate an analysis report's evidence by using a standardized checklist to verify that supporting data directly aligns with the stated purpose and validates the final conclusions.

What limitations exist when applying a standardized review checklist to reporting documents?

A standardized review checklist for reporting documents requires manual application to assess purpose and evidence, meaning it guides the reviewer's evaluation rather than automatically fixing content gaps.