analyzing-research-documents

Extract decisions, constraints, and action items from research documents.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill analyzing-research-documents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-research-documents
Source: https://github.com/samjhecht/wrangler/tree/main/skills/analyzing-research-documents
Command: npx skills add https://github.com/samjhecht/wrangler --skill analyzing-research-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently extracts high-value decisions, constraints, and action items from RCAs, design docs, and memos, filtering noise to deliver targeted guidance.

Core Features & Use Cases

  • Identify decisions, trade-offs, constraints, and action items
  • Distill technical specifics and open questions
  • Produce a concise analysis with conclusions and next steps

Quick Start

  • Provide a document path; output a structured analysis of key decisions and actionable items

Frequently Asked Questions about analyzing-research-documents

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

FAQPage Schema
How do I extract key decisions and action items from research documents?

Extract actionable insights by identifying decisions, trade-offs, constraints, and action items from research documents like RCAs, design docs, and memos. Provide the document path to receive a structured analysis that filters noise and surfaces high-value conclusions and next steps.

What types of documents can I analyze for insights?

Analyze research papers, root cause analyses (RCAs), design documents, and engineering memos. The Skill handles documents in engineering and product contexts, extracting technical specifications, decisions, constraints, and implementation guidance while filtering irrelevant content.

Can I use this to capture constraints and technical specifications from design docs?

Yes. The Skill captures constraints, technical specifications, and implementation details from design documents alongside decisions and trade-offs. Output is structured and auditable, supporting both decision-making and implementation guidance.

How does this approach differ from manually reading documents?

Manual reading surfaces scattered details; this Skill aggressively filters noise to deliver targeted, structured analysis. It systematically identifies decisions, trade-offs, constraints, and action items in a format optimized for decision support and implementation.

What output format does the analysis produce?

The analysis produces structured, auditable output that captures decisions, constraints, action items, technical specifics, and open questions in a concise format. Results are designed to support downstream decision-making and implementation guidance.