review-focus

Generate a structured reviewer's guide highlighting key decisions and assumptions from long-form documents.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/xinye1/xl-skills --skill review-focus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-focus
Source: https://github.com/xinye1/xl-skills/tree/main/skills/review-focus
Command: npx skills add https://github.com/xinye1/xl-skills --skill review-focus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of cognitive overload and rubber-stamping when reviewing long, complex documents by filtering out noise and highlighting critical decision points.

Core Features & Use Cases

  • Decision Filtering: Automatically extracts and ranks high-impact decisions that require product owner judgement.
  • Assumption Transparency: Identifies implicit defaults and assumptions made during document creation for quick veto-scanning.
  • Use Case: When presenting a 50-page technical specification or project plan, use this skill to generate a one-screen reviewer's guide that allows the stakeholder to focus only on risks, costs, and irreversible choices.

Quick Start

Use the review-focus skill to generate a reviewer guide for the attached project specification document.

Frequently Asked Questions about review-focus

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

FAQPage Schema
How do I extract key decisions from a long technical specification for stakeholder review?

To extract key decisions from a technical specification, you need a structured reviewer's guide that filters out noise and automatically ranks high-impact choices. This minimizes cognitive load by highlighting only risks, costs, and irreversible choices for stakeholder sign-off.

What is the best way to identify implicit assumptions in a project plan before sign-off?

Identifying implicit assumptions in a project plan requires assumption transparency, which extracts defaults made during document creation for quick veto-scanning. This allows stakeholders to focus on high-level judgement points rather than reading the entire document.

How do I generate a reviewer's guide for a 50-page research report?

Generating a reviewer's guide for a long research report involves filtering complex documents into a one-screen summary. It targets critical decision points and skimmable sections to prevent cognitive overload and rubber-stamping during the review process.

Can I use automated decision filtering to minimize cognitive load for product owners reviewing complex documents?

Automated decision filtering minimizes cognitive load for product owners by extracting and ranking high-impact decisions from complex documents. It creates a focused reviewer's guide that requires judgement only on specific risks and irreversible choices.

When do I need a structured reviewer's guide for technical specifications?

You need a structured reviewer's guide for technical specifications when presenting long, complex documents to stakeholders. It is essential when documents contain high-level decisions, implicit assumptions, and risks that require focused stakeholder sign-off to prevent rubber-stamping.