analyze

Analyze raw documents for clarity across eight categories and ask questions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/686f6c61/PSPO-Agent --skill analyze-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/686f6c61/PSPO-Agent/tree/main/skills/analyze
Command: npx skills add https://github.com/686f6c61/PSPO-Agent --skill analyze-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill clarifies raw documents (briefs, emails, PRDs) by interrogating them to achieve an 80% clarity score across 8 key categories, replacing the need for manual discovery when a document is provided.

Core Features & Use Cases

  • Automated Requirement Analysis: Analyzes provided text or documents to identify gaps and ambiguities.
  • Clarity Assessment: Evaluates document clarity across 8 predefined categories, providing a percentage score.
  • Guided Questioning: Asks targeted questions to resolve ambiguities and improve clarity.
  • Use Case: You have a draft product brief. Use this Skill to analyze it, identify areas needing more detail, and get specific questions to refine the requirements before proceeding to story generation.

Quick Start

Analyze the provided document by executing the analyze skill.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I analyze a product brief to identify missing requirements?

Analyzing a product brief involves interrogating the raw document to identify gaps and ambiguities, assessing clarity across eight key categories to reach an 80% clarity score.

Can I use a raw PRD draft for automated requirement refinement?

Requirement refinement works with raw PRDs by interrogating the document to evaluate clarity across eight categories and asking targeted questions to resolve specific ambiguities.

What is the best way to clarify ambiguities in an email before story generation?

Clarifying ambiguities in an email requires guided questioning that targets document gaps, automatically transitioning to story generation once an 80% clarity threshold is achieved.

Does document clarity analysis replace the manual discovery process?

Document clarity analysis replaces the manual discovery process when a starting document is provided, interrogating it to assess clarity and resolve ambiguities before proceeding.

How does guided questioning improve requirement refinement for raw documents?

Guided questioning improves requirement refinement by asking prioritized questions to resolve ambiguities, evaluating the document across eight predefined categories to achieve 80% clarity.

When should I not use automated requirement analysis for my brief?

Automated requirement analysis should not be used when you lack a starting document, as it replaces the discovery process by interrogating existing briefs, emails, or PRDs for clarity.