skills.rest
ramybarsoum
ramybarsoumCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-doc-review-panel

Review feature docs from seven perspectives to surface gaps and conflicts.

Updated Apr 10, 2026
Search Tags:#documentation#review#stakeholder#prd#product-management#multidisciplinary#feature-doc
One-click install
npx skills add https://github.com/ramybarsoum/RStack-V0 --skill feature-doc-review-panel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-doc-review-panel
Source: https://github.com/ramybarsoum/RStack-V0/tree/main/skill/feature-doc-review-panel
Command: npx skills add https://github.com/ramybarsoum/RStack-V0 --skill feature-doc-review-panel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-agent Feature Doc review provides comprehensive feedback from seven perspectives in parallel to surface gaps and conflicts before stakeholder review.

Core Features & Use Cases

  • 7 perspectives: eng, design, exec, legal, UX research, skeptic, customer voice
  • Parallel reviews with consolidated insights and alignment validation
  • Subset perspective reviews (e.g., eng, design, exec) for focused feedback

Quick Start

Run /feature-doc-review-panel on your latest PRD to get multi-perspective feedback.

Frequently Asked Questions about feature-doc-review-panel

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

FAQPage Schema
How do I get multi-perspective feedback on a feature doc or PRD before stakeholder review?▼

Multi-perspective feature doc review evaluates your PRD from seven distinct viewpoints—engineering, design, executive, legal, UX research, skeptic, and customer voice—to surface gaps and conflicts before stakeholder review.

What is the best way to identify conflicting assumptions in a product roadmap?▼

Identifying conflicting assumptions in a product roadmap requires parallel reviews from multidisciplinary perspectives that aggregate insights, validate alignment, and explicitly surface conflicts for resolution.

Can I run a feature doc review using only specific perspectives like engineering and design?▼

Yes, you can run subset perspective reviews for focused feedback, selecting only specific viewpoints such as engineering, design, and executive to target particular cross-functional concerns.

Does multi-agent product doc review work for design briefs and UX research documents?▼

Multi-agent product doc review works across product documents including design briefs, PRDs, and roadmaps, applying cross-functional feedback wherever multidisciplinary stakeholder alignment is required.

How do I validate cross-functional alignment across engineering, legal, and executive perspectives?▼

Validating cross-functional alignment involves running parallel reviews from engineering, legal, and executive perspectives, then consolidating the aggregated insights to check for consistent assumptions and requirements.

When do I need a multi-perspective review for a feature document?▼

You need a multi-perspective review for a feature document when cross-functional feedback is required from multiple stakeholders to ensure comprehensive coverage of engineering, design, legal, and customer concerns.

Related Skills

Explore More Product & Management Skills→
pisithrpspisithrps

prd-draft

Generate concise 1-2 page PRDs from feature briefs and save to outputs/prds/.

Community
Advanced
Chulf58Chulf58

forge:approve

Approve pending FORGE gates and update run status to completed.

Community
Advanced
edwardmonteiroedwardmonteiro

delivery.roadmap

Translate strategy into a sequenced delivery roadmap with risks and stakeholder communication.

Community
Basic
coalesce-labscoalesce-labs
20

prd-review-panel

Coordinate seven parallel sub-agents to review a PRD and synthesize feedback.

Official
Advanced