se-doc-review

Surface role-specific issues in requirements or plan documents via multi-persona analysis.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-doc-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-doc-review
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-doc-review
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-doc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams improve the quality and consistency of requirements or plan documents by orchestrating parallel persona reviews that surface role-specific issues, recommendations, and open questions.

Core Features & Use Cases

  • Parallel persona analysis surfaces discipline-specific concerns (coherence, feasibility, design, security) in requirements and plans.
  • Open Questions workflow defers unresolved findings to a shared Deferred / Open Questions section for collaborative follow-up.
  • Synthesized presentation and reporting provide a structured handoff to stakeholders and decision-makers.

Quick Start

Run the skill on a requirements or plan document to surface role-specific issues using parallel persona reviewers.

Frequently Asked Questions about se-doc-review

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

FAQPage Schema
How do I review requirements documents from multiple perspectives?

Review requirements documents from multiple perspectives by orchestrating parallel persona analysis that surfaces role-specific issues across disciplines like coherence, feasibility, design, and security. This multi-persona approach ensures comprehensive coverage of potential document flaws.

How does multi-persona document review handle unresolved findings?

Multi-persona document review handles unresolved findings by routing them to a shared Open Questions section. This defers unresolved items for collaborative follow-up rather than forcing immediate resolution during the initial analysis pass.

What is the best way to classify issues found during plan document analysis?

The best way to classify issues found during plan document analysis is to apply safe_auto, gated_auto, and manual action categories. This classification system routes findings appropriately based on their required level of intervention and automation safety.

Can I generate a synthesized report for stakeholder handoffs after a document review?

Yes, you can generate a synthesized report for stakeholder handoffs after a document review. The process provides a structured presentation with clearly labeled FYI observations to support decision-makers receiving the reviewed requirements.

Does this multi-persona analysis approach work for both requirements and plan documents?

Yes, this multi-persona analysis approach works for both requirements and plan documents. It operates across various document types to consistently surface role-specific issues and defer unresolved items to Open Questions.