prd-draft-review-workflow-v1

Analyze individual PRD documents across 6 dimensions with vision support for images. Use when (1) analyzing a PRD document's core problem, boundaries, and boundary-external issues, (2) tracking whether issues are resolved in later versions, (3) extracting key parameters and solution highlights from technical PRDs, (4) scoring document quality, (5) understanding flowcharts, architecture diagrams, UI mockups, or screenshots embedded in PRD documents. Also use when a user mentions 'per-doc analysis', 'boundary analysis', 'issue tracking', 'document review', or 'PRD quality scoring'.

Classify and overview a batch of Markdown PRD documents by category, build version evolution chains, and detect inter-document dependencies. Use when categorizing PRD or requirement documents by topic, extracting version numbers, finding document relationships, or generating overview summaries. Also use when you need to understand the structure of a document set before deep analysis, or when a user mentions 'overview', 'categorize', 'classify documents', 'version chain', or 'document relationships'.

Convert DOCX to Markdown with embedded Excel table conversion and image extraction. Use when (1) converting .docx files to Markdown, especially those containing embedded Excel spreadsheets, (2) extracting images from Word documents to local files with relative paths, (3) batch processing multiple DOCX files, (4) optionally converting Markdown to PDF with Chinese font support.

Generate structured Markdown and PDF reports from analysis results. Use when (1) rendering per-document analysis results into a readable report, (2) generating a full system review report from 7-dimension analysis, (3) producing a next-directions report from evolution tracking and gap analysis, (4) generating a PM development suggestion report with scoring cards, (5) producing a PRD draft report based on historical analysis, (6) creating Mermaid diagrams for evolution chains and dependency graphs, (7) converting Markdown reports to PDF. Also use when a user mentions 'generate report', 'export report', 'PDF report', 'review report', or 'analysis report'.

Discover requirement insights through evolution tracking and gap analysis. Use when (1) tracking how boundary-external issues are resolved across version chains, (2) building feature coverage matrices to identify uncovered functionality, (3) visualizing requirement evolution with Mermaid diagrams, (4) finding requirement gaps and overlaps, (5) generating next-direction recommendations based on unresolved issues and missing features. Also use when a user mentions 'evolution tracking', 'gap analysis', 'coverage matrix', 'requirement insights', 'unresolved issues', or 'feature coverage'.

Systematic 7-dimension review of a batch of PRD documents with multiple output modes. Use when (1) conducting a full system-level review across business value, architecture, competition, product strategy, tech evolution, PM assessment, and action planning, (2) generating next-direction recommendations for a requirement set, (3) evaluating PM writing quality and product thinking from requirement documents, (4) drafting a new PRD based on historical analysis of related documents, (5) producing any of these outputs: full_report, next_directions, quality_assessment, prd_draft. Also use when a user mentions 'system review', '7-dimension review', 'PM assessment', 'requirement review report', 'quality evaluation', or 'PRD draft generation'.