the-product-playbook 2.5.2 → 2.6.0

package/README.es.md

@@ -24,7 +24,8 @@ The Product Playbook es un **Skill de Claude AI** que te guía sistemáticamente
 - 🔄 **Motor de propagación de cambios** — modifica cualquier paso y todos los outputs downstream se actualizan automáticamente
 - 📎 **Integración inteligente de archivos** — sube datos, capturas de pantalla o documentos; la IA los integra automáticamente en el paso relevante
 - 🔗 **Handoff de desarrollo** — genera CLAUDE.md + TASKS.md + TICKETS.md para un handoff fluido al desarrollo en Claude Code
-- 📊 **Output multi-formato** — reportes HTML, PRDs, presentaciones PowerPoint, paquetes de handoff de desarrollo
+- 📊 **Output multi-formato** — PDF (con marcadores), reportes HTML, documentos Word, presentaciones PowerPoint, paquetes de handoff de desarrollo
+- 📄 **Importación inteligente de documentos** — análisis de PDF en tres capas (extracción de texto → Claude Vision → OCR como respaldo), soporte DOCX/PPTX
 
 **Activa todo el flujo con una sola oración:**
 
@@ -153,7 +154,13 @@ the-product-playbook/
     ├── 07-dev-handoff.md             # Handoff de desarrollo: CLAUDE.md + TASKS.md + Arquitectura
     ├── 08-security-checklist.md      # OWASP Top 10 + CORS + CSP + Arquitectura de seguridad
     ├── rules-context.md              # Reglas de acumulación de contexto de producto cross-sesión
-    └── rules-*.md                    # Reglas de pasos por modo + reglas de progreso/cambio/integración de archivos
+    ├── rules-document-tools.md       # Gestión de dependencias de herramientas de conversión de documentos
+    ├── rules-import-document.md      # Análisis de PDF en tres capas + importación DOCX/PPTX
+    ├── rules-export-document.md      # Exportación multi-formato (PDF/DOCX/PPTX)
+    ├── rules-*.md                    # Reglas de pasos por modo + reglas de progreso/cambio/integración de archivos
+    └── templates/
+        ├── prd-style.css             # CSS profesional de grado impresión para exportación PDF
+        └── report-style.css          # CSS de optimización de impresión para reporte HTML → PDF
 ```
 
 ---
@@ -261,6 +268,28 @@ Genera un paquete completo de handoff de desarrollo e inicia desarrollo en Claud
 > Por favor lee CLAUDE.md y TASKS.md, comienza ejecutando la Fase 0
 ```
 
+### 📄 Importación y Exportación de Documentos
+
+**Importa** cualquier documento existente al flujo de planificación — sin copiar y pegar manualmente:
+
+```
+PDF (digital)       → extracción de texto pymupdf (instantáneo, gratuito)
+PDF (vectorial/escaneo) → análisis semántico Claude Vision (mejor calidad)
+PDF (respaldo)      → Tesseract OCR (funciona offline)
+DOCX / PPTX         → conversión Pandoc
+```
+
+**Exporta** outputs de planificación a formatos profesionales:
+
+```
+/export pdf   → renderizado Playwright + marcadores pikepdf (CJK perfecto)
+/export docx  → Pandoc + plantilla de referencia
+/export pptx  → generación de diapositivas Pandoc
+/export html  → reporte HTML interactivo (existente)
+```
+
+> **¿Por qué PDF via Playwright?** WeasyPrint produce texto CJK ilegible. Playwright (Chromium) renderiza perfectamente — verificado en producción con documentos en chino tradicional.
+
 ### 🔥 Planifica Directamente sobre Sistemas Existentes (Funcionalidad Estrella del Modo Build)
 
 Lanza el **Modo Build** dentro de un directorio de proyecto existente — Claude Code lee tu codebase mientras hace planificación de producto, fusionando efectivamente **planificación de producto** y **evaluación de factibilidad técnica** en un solo flujo:
@@ -407,6 +436,10 @@ cp -r the-product-playbook/commands/* ~/.claude/commands/
 - `Generar PRD` — entrega de ingeniería (incluye diagramas de flujo + DB Schema + wireframes)
 - `Generar presentación` — presentación PowerPoint
 - `Iniciar desarrollo` — paquete de handoff de desarrollo (CLAUDE.md + TASKS.md)
+- `/export pdf` — exportar como PDF con tipografía profesional, portada, índice y marcadores
+- `/export docx` — exportar como documento Word
+- `/export pptx` — exportar como diapositivas PowerPoint
+- `/parse [file]` — analizar un PDF/DOCX/PPTX en Markdown para uso en planificación
 
 #### Comandos de Análisis
 - `Ejecutar evaluación de completitud` — evaluar cobertura de planificación

package/README.ja.md

@@ -24,7 +24,8 @@ The Product Playbookは、ゼロから一まで体系的にプロダクト企画
 - 🔄 **変更伝播エンジン** — 任意のステップを修正すると下流の全出力が自動更新
 - 📎 **スマートファイル統合** — データ、スクリーンショット、ドキュメントをアップロードするとAIが関連ステップに自動統合
 - 🔗 **開発ハンドオフ** — CLAUDE.md + TASKS.md + TICKETS.mdを生成してClaude Code開発にシームレスに接続
-- 📊 **マルチフォーマット出力** — HTMLレポート、PRD、PowerPointデッキ、開発ハンドオフパッケージ
+- 📊 **マルチフォーマット出力** — PDF（ブックマーク付き）、HTMLレポート、Wordドキュメント、PowerPointデッキ、開発ハンドオフパッケージ
+- 📄 **スマートドキュメントインポート** — 三層PDFパース（テキスト抽出 → Claude Vision → OCRフォールバック）、DOCX/PPTXサポート
 
 **一文でフロー全体をトリガー：**
 
@@ -154,7 +155,13 @@ the-product-playbook/
     ├── 07-dev-handoff.md             # 開発ハンドオフ：CLAUDE.md + TASKS.md + アーキテクチャ
     ├── 08-security-checklist.md      # OWASP Top 10 + CORS + CSP + セキュリティアーキテクチャ
     ├── rules-context.md              # クロスセッションプロダクトコンテキスト蓄積ルール
-    └── rules-*.md                    # モードステップルール + 進捗/変更/ファイル統合ルール
+    ├── rules-document-tools.md       # ドキュメント変換ツール依存管理
+    ├── rules-import-document.md      # 三層PDFパース + DOCX/PPTXインポート
+    ├── rules-export-document.md      # マルチフォーマットエクスポート（PDF/DOCX/PPTX）
+    ├── rules-*.md                    # モードステップルール + 進捗/変更/ファイル統合ルール
+    └── templates/
+        ├── prd-style.css             # プロフェッショナル印刷グレードCSS（PDFエクスポート用）
+        └── report-style.css          # 印刷最適化CSS（HTMLレポート → PDF）
 ```
 
 ---
@@ -262,6 +269,28 @@ MVPを修正 → User Stories、DBスキーマ、プロダクトスペックサ
 > CLAUDE.mdとTASKS.mdを読んで、Phase 0の実行を開始してください
 ```
 
+### 📄 ドキュメントインポート＆エクスポート
+
+**インポート** — 既存のドキュメントを企画フローに直接取り込み、手動コピペ不要：
+
+```
+PDF（デジタル）    → pymupdfテキスト抽出（即座、無料）
+PDF（ベクター/スキャン） → Claude Visionセマンティックパース（最高品質）
+PDF（フォールバック） → Tesseract OCR（オフライン対応）
+DOCX / PPTX       → Pandoc変換
+```
+
+**エクスポート** — 企画アウトプットをプロフェッショナルなフォーマットに：
+
+```
+/export pdf   → Playwrightレンダリング + pikepdfブックマーク（CJK完全対応）
+/export docx  → Pandoc + リファレンステンプレート
+/export pptx  → Pandocスライド生成
+/export html  → インタラクティブHTMLレポート（既存）
+```
+
+> **なぜPlaywrightでPDF？** WeasyPrintはCJKテキストが文字化けします。Playwright（Chromium）は完璧にレンダリング — 繁體中文ドキュメントで本番環境検証済み。
+
 ### 🔥 既存システム上で直接企画（ビルドモードのキラー機能）
 
 既存プロジェクトディレクトリ内で**ビルドモード**を起動 — Claude Codeがコードベースを読みながらプロダクト企画を行い、**プロダクト企画**と**技術的実現可能性評価**を単一フローに統合：
@@ -408,6 +437,10 @@ cp -r the-product-playbook/commands/* ~/.claude/commands/
 - `PRDを生成` — エンジニアリングハンドオフ（フローチャート + DBスキーマ + ワイヤーフレーム付き）
 - `プレゼンを生成` — PowerPointプレゼンテーション
 - `開発を始めて` — 開発ハンドオフパッケージ（CLAUDE.md + TASKS.md）
+- `/export pdf` — プロフェッショナルなタイポグラフィ、表紙、目次、ブックマーク付きPDFとしてエクスポート
+- `/export docx` — Wordドキュメントとしてエクスポート
+- `/export pptx` — PowerPointスライドとしてエクスポート
+- `/parse [file]` — PDF/DOCX/PPTXをMarkdownにパースして企画に利用
 
 #### 分析コマンド
 - `完成度チェックを実行` — 企画カバレッジの評価

package/README.ko.md

@@ -24,7 +24,8 @@ The Product Playbook은 제로부터 원까지 제품 기획 전 과정을 체
 - 🔄 **변경 전파 엔진** — 어떤 단계든 수정하면 모든 하위 산출물이 자동 업데이트
 - 📎 **스마트 파일 통합** — 데이터, 스크린샷, 문서를 업로드하면 AI가 해당 단계에 자동 통합
 - 🔗 **개발 핸드오프** — CLAUDE.md + TASKS.md + TICKETS.md를 생성하여 Claude Code 개발로 원활하게 연결
-- 📊 **다중 형식 출력** — HTML 보고서, PRD, PowerPoint 덱, 개발 핸드오프 패키지
+- 📊 **다중 형식 출력** — PDF(북마크 포함), HTML 보고서, Word 문서, PowerPoint 덱, 개발 핸드오프 패키지
+- 📄 **스마트 문서 가져오기** — 3단계 PDF 파싱(텍스트 추출 → Claude Vision → OCR 폴백), DOCX/PPTX 지원
 
 **한 문장으로 전체 플로우를 트리거하세요:**
 
@@ -153,7 +154,13 @@ the-product-playbook/
     ├── 07-dev-handoff.md             # 개발 핸드오프: CLAUDE.md + TASKS.md + Architecture
     ├── 08-security-checklist.md      # OWASP Top 10 + CORS + CSP + 보안 아키텍처
     ├── rules-context.md              # 세션 간 제품 컨텍스트 축적 규칙
-    └── rules-*.md                    # 모드 단계 규칙 + 진행/변경/파일 통합 규칙
+    ├── rules-document-tools.md       # 문서 변환 도구 의존성 관리
+    ├── rules-import-document.md      # 3단계 PDF 파싱 + DOCX/PPTX 가져오기
+    ├── rules-export-document.md      # 다중 형식 내보내기(PDF/DOCX/PPTX)
+    ├── rules-*.md                    # 모드 단계 규칙 + 진행/변경/파일 통합 규칙
+    └── templates/
+        ├── prd-style.css             # 전문 인쇄 등급 CSS(PDF 내보내기용)
+        └── report-style.css          # 인쇄 최적화 CSS(HTML 보고서 → PDF)
 ```
 
 ---
@@ -261,6 +268,28 @@ MVP 수정  → User Stories, DB Schema, 제품 스펙 요약 자동 업데이
 > CLAUDE.md와 TASKS.md를 읽고, Phase 0 실행 시작
 ```
 
+### 📄 문서 가져오기 및 내보내기
+
+**가져오기** — 기존 문서를 기획 플로우에 직접 투입, 수동 복사 붙여넣기 불필요:
+
+```
+PDF (디지털)       → pymupdf 텍스트 추출 (즉시, 무료)
+PDF (벡터/스캔)    → Claude Vision 시맨틱 파싱 (최고 품질)
+PDF (폴백)         → Tesseract OCR (오프라인 가능)
+DOCX / PPTX        → Pandoc 변환
+```
+
+**내보내기** — 기획 산출물을 전문적 형식으로:
+
+```
+/export pdf   → Playwright 렌더링 + pikepdf 북마크 (CJK 완벽 지원)
+/export docx  → Pandoc + 참조 템플릿
+/export pptx  → Pandoc 슬라이드 생성
+/export html  → 인터랙티브 HTML 보고서 (기존)
+```
+
+> **왜 Playwright로 PDF를?** WeasyPrint은 CJK 텍스트가 깨집니다. Playwright(Chromium)는 완벽하게 렌더링됩니다 — 번체 중국어 문서로 프로덕션 환경에서 검증 완료.
+
 ### 🔥 기존 시스템 위에서 바로 기획 (빌드 모드 킬러 피처)
 
 기존 프로젝트 디렉토리에서 **빌드 모드**를 실행하면 — Claude Code가 코드베이스를 읽으면서 제품 기획을 수행하여, **제품 기획**과 **기술 실현 가능성 평가**를 단일 플로우로 병합합니다:
@@ -407,6 +436,10 @@ cp -r the-product-playbook/commands/* ~/.claude/commands/
 - `PRD 생성` — 엔지니어링 핸드오프 (플로우차트 + DB Schema + 와이어프레임 포함)
 - `덱 생성` — PowerPoint 프레젠테이션
 - `개발 시작` — 개발 핸드오프 패키지 (CLAUDE.md + TASKS.md)
+- `/export pdf` — 전문 타이포그래피, 표지, 목차 및 북마크가 포함된 PDF로 내보내기
+- `/export docx` — Word 문서로 내보내기
+- `/export pptx` — PowerPoint 슬라이드로 내보내기
+- `/parse [file]` — PDF/DOCX/PPTX를 Markdown으로 파싱하여 기획에 활용
 
 #### 분석 명령
 - `완성도 점검 해 주세요` — 기획 커버리지 평가

package/README.md

@@ -24,7 +24,8 @@ The Product Playbook is a **Claude AI Skill** that systematically guides you thr
 - 🔄 **Change propagation engine** — modify any step and all downstream outputs update automatically
 - 📎 **Smart file integration** — upload data, screenshots, or documents; the AI automatically integrates them into the relevant step
 - 🔗 **Dev handoff** — generates CLAUDE.md + TASKS.md + TICKETS.md for seamless handoff to Claude Code development
-- 📊 **Multi-format output** — HTML reports, PRDs, PowerPoint decks, dev handoff packages
+- 📊 **Multi-format output** — PDF (with bookmarks), HTML reports, Word docs, PowerPoint decks, dev handoff packages
+- 📄 **Smart document import** — three-layer PDF parsing (text extraction → Claude Vision → OCR fallback), DOCX/PPTX support
 
 **Trigger the entire flow with a single sentence:**
 
@@ -153,7 +154,13 @@ the-product-playbook/
     ├── 07-dev-handoff.md             # Dev handoff: CLAUDE.md + TASKS.md + Architecture
     ├── 08-security-checklist.md      # OWASP Top 10 + CORS + CSP + Security architecture
     ├── rules-context.md              # Cross-session product context accumulation rules
-    └── rules-*.md                    # Mode step rules + progress/change/file integration rules
+    ├── rules-document-tools.md       # Document conversion tool dependency management
+    ├── rules-import-document.md      # Three-layer PDF parsing + DOCX/PPTX import
+    ├── rules-export-document.md      # Multi-format export (PDF/DOCX/PPTX)
+    ├── rules-*.md                    # Mode step rules + progress/change/file integration rules
+    └── templates/
+        ├── prd-style.css             # Professional print-grade CSS for PDF export
+        └── report-style.css          # Print optimization CSS for HTML report → PDF
 ```
 
 ---
@@ -261,6 +268,28 @@ Generate a complete dev handoff package and kick off Claude Code development wit
 > Please read CLAUDE.md and TASKS.md, start executing Phase 0
 ```
 
+### 📄 Document Import & Export
+
+**Import** any existing document into the planning flow — no manual copy-paste:
+
+```
+PDF (digital)   → pymupdf text extraction (instant, free)
+PDF (vector/scan) → Claude Vision semantic parsing (best quality)
+PDF (fallback)  → Tesseract OCR (offline capable)
+DOCX / PPTX     → Pandoc conversion
+```
+
+**Export** planning outputs to professional formats:
+
+```
+/export pdf   → Playwright rendering + pikepdf bookmarks (CJK-perfect)
+/export docx  → Pandoc + reference template
+/export pptx  → Pandoc slide generation
+/export html  → Interactive HTML report (existing)
+```
+
+> **Why PDF via Playwright?** WeasyPrint produces garbled CJK text. Playwright (Chromium) renders perfectly — verified in production with Traditional Chinese documents.
+
 ### 🔥 Plan Directly on Existing Systems (Build Mode Killer Feature)
 
 Launch **Build Mode** inside an existing project directory — Claude Code reads your codebase while doing product planning, effectively merging **product planning** and **technical feasibility assessment** into a single flow:
@@ -407,6 +436,10 @@ cp -r the-product-playbook/commands/* ~/.claude/commands/
 - `Generate PRD` — engineering handoff (includes flowcharts + DB Schema + wireframes)
 - `Generate deck` — PowerPoint presentation
 - `Start development` — dev handoff package (CLAUDE.md + TASKS.md)
+- `/export pdf` — export as PDF with professional typography, cover page, TOC, and bookmarks
+- `/export docx` — export as Word document
+- `/export pptx` — export as PowerPoint slides
+- `/parse [file]` — parse a PDF/DOCX/PPTX into Markdown for planning use
 
 #### Analysis Commands
 - `Run a completeness check` — assess planning coverage

package/README.zh-CN.md

@@ -24,7 +24,8 @@ The Product Playbook 是一个 **Claude AI Skill**，能够系统性地引导你
 - 🔄 **变更传播引擎** — 修改任何步骤，自动更新所有下游产出
 - 📎 **文件智慧整合** — 上传数据、截图、文件，AI 自动整合到对应步骤
 - 🔗 **开发衔接** — 产出 CLAUDE.md + TASKS.md + TICKETS.md，无缝衔接 Claude Code 开发
-- 📊 **多格式产出** — HTML 报告、PRD、PowerPoint、开发交接包
+- 📊 **多格式产出** — PDF（含书签）、HTML 报告、Word 文档、PowerPoint、开发交接包
+- 📄 **智慧文档导入** — 三层 PDF 解析（文字提取 → Claude Vision → OCR 兜底）、DOCX/PPTX 支持
 
 **用一句话触发整个流程：**
 
@@ -153,7 +154,13 @@ the-product-playbook/
     ├── 07-dev-handoff.md             # 开发衔接：CLAUDE.md + TASKS.md + 架构
     ├── 08-security-checklist.md      # OWASP Top 10 + CORS + CSP + 安全架构
     ├── rules-context.md              # 跨 Session 产品上下文累积规则
-    └── rules-*.md                    # 各模式步骤规则 + 进度/变更/文件整合规则
+    ├── rules-document-tools.md       # 文档转换工具依赖管理
+    ├── rules-import-document.md      # 三层 PDF 解析 + DOCX/PPTX 导入
+    ├── rules-export-document.md      # 多格式导出（PDF/DOCX/PPTX）
+    ├── rules-*.md                    # 各模式步骤规则 + 进度/变更/文件整合规则
+    └── templates/
+        ├── prd-style.css             # 专业印刷级 CSS（PDF 导出用）
+        └── report-style.css          # 打印优化 CSS（HTML 报告 → PDF）
 ```
 
 ---
@@ -261,6 +268,28 @@ the-product-playbook/
 > 请读取 CLAUDE.md 和 TASKS.md，开始执行 Phase 0
 ```
 
+### 📄 文档导入与导出
+
+**导入**任何现有文档到规划流程中 — 无需手动复制粘贴：
+
+```
+PDF（数字版）    → pymupdf 文字提取（即时、免费）
+PDF（矢量/扫描） → Claude Vision 语义解析（最佳品质）
+PDF（兜底）      → Tesseract OCR（可离线使用）
+DOCX / PPTX     → Pandoc 转换
+```
+
+**导出**规划成果为专业格式：
+
+```
+/export pdf   → Playwright 渲染 + pikepdf 书签（CJK 完美支持）
+/export docx  → Pandoc + 参考模板
+/export pptx  → Pandoc 幻灯片生成
+/export html  → 交互式 HTML 报告（既有功能）
+```
+
+> **为什么用 Playwright 输出 PDF？** WeasyPrint 会产生 CJK 乱码。Playwright（Chromium）渲染完美 — 已在生产环境以繁体中文文档验证。
+
 ### 🔥 既有系统直接规划（Build 模式杀手级用法）
 
 在既有专案目录中启动 **直接实作模式**，Claude Code 会一边读取你的 codebase 一边做产品规划 — 等于把**产品规划**和**技术可行性评估**合在同一个流程里完成：
@@ -407,6 +436,10 @@ cp -r the-product-playbook/commands/* ~/.claude/commands/
 - `产出 PRD` — 工程师交付包（含流程图 + DB Schema + Wireframe）
 - `产出简报` — PowerPoint 简报
 - `进入开发` — 开发交接包（CLAUDE.md + TASKS.md）
+- `/export pdf` — 导出为 PDF，含专业排版、封面、目录及书签
+- `/export docx` — 导出为 Word 文档
+- `/export pptx` — 导出为 PowerPoint 演示文稿
+- `/parse [file]` — 解析 PDF/DOCX/PPTX 为 Markdown 以供规划使用
 
 #### 分析指令
 - `帮我做完整性评估` — 评估规划完整度

package/README.zh-TW.md

@@ -24,7 +24,8 @@ The Product Playbook 是一個 **Claude AI Skill**，能夠系統性地引導你
 - 🔄 **變更傳播引擎** — 修改任何步驟，自動更新所有下游產出
 - 📎 **檔案智慧整合** — 上傳數據、截圖、文件，AI 自動整合到對應步驟
 - 🔗 **開發銜接** — 產出 CLAUDE.md + TASKS.md + TICKETS.md，無縫銜接 Claude Code 開發
-- 📊 **多格式產出** — HTML 報告、PRD、PowerPoint、開發交接包
+- 📊 **多格式產出** — PDF（含書籤）、HTML 報告、Word 文件、PowerPoint、開發交接包
+- 📄 **智慧文件匯入** — 三層 PDF 解析（文字擷取 → Claude Vision → OCR 備援）、DOCX/PPTX 支援
 
 **用一句話觸發整個流程：**
 
@@ -153,7 +154,13 @@ the-product-playbook/
     ├── 07-dev-handoff.md             # 開發銜接：CLAUDE.md + TASKS.md + 架構
     ├── 08-security-checklist.md      # OWASP Top 10 + CORS + CSP + 安全架構
     ├── rules-context.md              # 跨 Session 產品上下文累積規則
-    └── rules-*.md                    # 各模式步驟規則 + 進度/變更/檔案整合規則
+    ├── rules-document-tools.md       # 文件轉換工具依賴管理
+    ├── rules-import-document.md      # 三層 PDF 解析 + DOCX/PPTX 匯入
+    ├── rules-export-document.md      # 多格式匯出（PDF/DOCX/PPTX）
+    ├── rules-*.md                    # 各模式步驟規則 + 進度/變更/檔案整合規則
+    └── templates/
+        ├── prd-style.css             # 專業印刷級 CSS（PDF 匯出用）
+        └── report-style.css          # 列印最佳化 CSS（HTML 報告 → PDF）
 ```
 
 ---
@@ -261,6 +268,28 @@ the-product-playbook/
 > 請讀取 CLAUDE.md 和 TASKS.md，開始執行 Phase 0
 ```
 
+### 📄 文件匯入與匯出
+
+**匯入**任何現有文件到規劃流程中 — 無需手動複製貼上：
+
+```
+PDF（數位）      → pymupdf 文字擷取（即時、免費）
+PDF（向量/掃描） → Claude Vision 語意解析（最佳品質）
+PDF（備援）      → Tesseract OCR（可離線使用）
+DOCX / PPTX     → Pandoc 轉換
+```
+
+**匯出**規劃成果為專業格式：
+
+```
+/export pdf   → Playwright 渲染 + pikepdf 書籤（CJK 完美支援）
+/export docx  → Pandoc + 參考模板
+/export pptx  → Pandoc 投影片生成
+/export html  → 互動式 HTML 報告（既有功能）
+```
+
+> **為什麼用 Playwright 輸出 PDF？** WeasyPrint 會產生 CJK 亂碼。Playwright（Chromium）渲染完美 — 已在正式環境以繁體中文文件驗證。
+
 ### 🔥 既有系統直接規劃（Build 模式殺手級用法）
 
 在既有專案目錄中啟動 **直接實作模式**，Claude Code 會一邊讀取你的 codebase 一邊做產品規劃 — 等於把**產品規劃**和**技術可行性評估**合在同一個流程裡完成：
@@ -407,6 +436,10 @@ cp -r the-product-playbook/commands/* ~/.claude/commands/
 - `產出 PRD` — 工程師交付包（含流程圖 + DB Schema + Wireframe）
 - `產出簡報` — PowerPoint 簡報
 - `進入開發` — 開發交接包（CLAUDE.md + TASKS.md）
+- `/export pdf` — 匯出為 PDF，含專業排版、封面、目錄及書籤
+- `/export docx` — 匯出為 Word 文件
+- `/export pptx` — 匯出為 PowerPoint 簡報
+- `/parse [file]` — 解析 PDF/DOCX/PPTX 為 Markdown 以供規劃使用
 
 #### 分析指令
 - `幫我做完整性評估` — 評估規劃完整度

package/i18n/en/references/rules-build.md

@@ -121,6 +121,25 @@ Rationale: [Comprehensive judgment based on impact scope, complexity, and risk]
 
 **Feature development spec**: Problem statement → Selected solution + rationale → Impact scope → Execution scope + acceptance criteria → Risk list
 
+### Incremental Document Output (when source document is available)
+
+If the user uploaded a source document (PRD, spec, etc.) during the process:
+
+1. **Incremental version** (default when source document exists):
+   - Insert/modify sections in the original document structure
+   - Maintain the original file's format, style, and naming conventions
+   - New content marked with `[NEW]`
+   - Modified content marked with `[UPDATED]` with original preserved as reference
+   - Sections unrelated to the new feature remain completely untouched
+
+2. **Standalone version** (when no source document):
+   - Use the standard Feature development spec format (as defined above)
+
+3. **Ask the user before generating**:
+   "I detected that you uploaded a [document type]. How would you like the output?
+    A) Incremental update on the original document (recommended)
+    B) Standalone feature development spec"
+
 ### Reference Loading Instructions
 
 | Step | Reference File |

package/i18n/en/references/rules-commands.md

@@ -88,5 +88,7 @@ When the user says "skip user research," "problem is already known," "go straigh
 | `"Pause"` / `"Save"` / `"Do something else first"` | Save progress per `references/rules-progress.md` |
 | `"Continue"` / `"Back to planning"` | Resume per `references/rules-progress.md` |
 | `"Clear progress"` / `"Start over"` | Delete progress file and start from scratch |
+| `/export [format]` | Export to specified format. format = `pdf` / `docx` / `pptx` / `html` / `md`. Read `references/rules-export-document.md`. On first use, load `references/rules-document-tools.md` first to check tools. |
+| `/parse [file]` | Parse an uploaded document to Markdown. Supports PDF / DOCX / PPTX / images. Read `references/rules-import-document.md`. On first use, load `references/rules-document-tools.md` first to check tools. |
 
 **Context-aware command hints**: After each step is completed, proactively suggest 2-3 of the most relevant available commands based on the current progress.

package/i18n/en/references/rules-document-tools.md

@@ -0,0 +1,126 @@
+# Document Conversion Tool Dependency Management
+
+> Loaded on first trigger of `/export` or `/parse` command.
+
+## Dependency Tiers
+
+| Tier | Tool | Purpose | Installation | Size |
+|------|------|---------|-------------|------|
+| **Core (Zero Install)** | Claude Read tool (Vision) | PDF semantic parsing | Built-in | 0 |
+| **Core (Zero Install)** | Playwright MCP | PDF rendering | Built-in | 0 |
+| **Basic** | pymupdf (fitz) | PDF text extraction + image rendering | `pip3 install --break-system-packages pymupdf` | ~23MB |
+| **Basic** | pikepdf | PDF bookmark injection + metadata | `pip3 install --break-system-packages pikepdf` | ~5MB |
+| **Extended** | pandoc | DOCX / PPTX conversion | `brew install pandoc` | ~50MB |
+| **Fallback** | tesseract + chi_tra | Offline OCR (when Vision is unavailable) | `brew install tesseract tesseract-lang` | ~150MB |
+| **Advanced** | python-docx | High-quality DOCX output | `pip3 install --break-system-packages python-docx` | ~5MB |
+
+## Startup Detection Flow
+
+When the user first triggers a document conversion feature, detect and install as needed in the following order:
+
+### Step 1: Determine Which Tools Are Needed
+
+| User Action | Required Tools |
+|-------------|---------------|
+| `/export pdf` | pymupdf + pikepdf + Playwright MCP |
+| `/export docx` or `/export pptx` | pandoc |
+| `/parse [PDF file]` | pymupdf (+ Claude Vision or tesseract) |
+| `/parse [DOCX/PPTX file]` | pandoc |
+
+### Step 2: Detect Installed Tools
+
+Run the following Bash commands (silent detection, no output displayed):
+
+```bash
+# pymupdf
+python3 -c "import fitz; print(fitz.version)" 2>/dev/null && echo "pymupdf: OK" || echo "pymupdf: MISSING"
+
+# pikepdf
+python3 -c "import pikepdf; print(pikepdf.__version__)" 2>/dev/null && echo "pikepdf: OK" || echo "pikepdf: MISSING"
+
+# pandoc
+which pandoc >/dev/null 2>&1 && echo "pandoc: OK" || echo "pandoc: MISSING"
+
+# tesseract (only detect when explicitly needed)
+which tesseract >/dev/null 2>&1 && tesseract --list-langs 2>&1 | grep -q chi_tra && echo "tesseract: OK" || echo "tesseract: MISSING"
+```
+
+### Step 3: Auto-Install Missing Tools
+
+If missing tools are detected, display the following message and install automatically:
+
+```
+📦 Document conversion requires the following tools:
+  ☐ [Tool name] ([purpose], [size])
+  ...
+Installing, please wait...
+```
+
+Run installation commands in sequence:
+
+```bash
+# pymupdf + pikepdf (install together)
+pip3 install --break-system-packages pymupdf pikepdf
+
+# pandoc
+brew install pandoc
+
+# tesseract (only when offline OCR is needed)
+brew install tesseract tesseract-lang
+```
+
+After installation completes, display:
+```
+✅ Tool installation complete, continuing...
+```
+
+### Step 4: Detect Playwright MCP
+
+Playwright MCP is a core dependency for PDF rendering. Detection method:
+
+1. Attempt to call `mcp__plugin_playwright_playwright__browser_run_code`
+2. If MCP is available → use normally
+3. If MCP is unavailable (not connected) → display:
+
+```
+⚠️ Playwright MCP is not connected. PDF rendering requires the Playwright browser.
+Please do one of the following:
+  1. Start Playwright MCP (recommended)
+  2. Or run ! npx playwright install chromium to install local Chromium
+```
+
+**Playwright Fallback** (when MCP is unavailable):
+
+If the user has installed local Chromium, use Bash to run a Node.js script for PDF rendering:
+```bash
+node -e "
+const { chromium } = require('playwright');
+(async () => {
+  const browser = await chromium.launch();
+  const page = await browser.newPage();
+  await page.setContent(require('fs').readFileSync('/tmp/export.html', 'utf8'));
+  await page.pdf({ path: '${OUTPUT_PATH}', format: 'A4', printBackground: true,
+    margin: { top: '1.8cm', bottom: '1.8cm', left: '2cm', right: '2cm' } });
+  await browser.close();
+})();
+"
+```
+
+## Tool State Cache
+
+First detection results are recorded in memory (to avoid repeated detection):
+- Within the same conversation session, confirmed installed tools are not re-detected
+- If installation fails, record the error message and retry on the next trigger
+
+## Platform Compatibility
+
+| Platform | pymupdf | pikepdf | pandoc | tesseract | Playwright |
+|----------|---------|---------|--------|-----------|------------|
+| macOS (Homebrew) | ✅ pip3 | ✅ pip3 | ✅ brew | ✅ brew | ✅ MCP/npx |
+| Linux (apt) | ✅ pip3 | ✅ pip3 | ✅ apt | ✅ apt | ✅ MCP/npx |
+| Windows (WSL) | ✅ pip3 | ✅ pip3 | ✅ choco | ✅ choco | ✅ MCP/npx |
+
+Automatically select the corresponding package manager based on the user's operating system. Detection method:
+```bash
+[[ "$(uname)" == "Darwin" ]] && echo "macOS" || echo "Linux"
+```

package/i18n/en/references/rules-end-of-flow.md

@@ -70,18 +70,29 @@ After completing the final integrated output, proactively ask:
 ```
 "The planning content has been fully integrated! Would you like me to generate any of the following documents?
 
-□ HTML planning report (suitable for sharing with everyone)
+□ Updated [document type] (incremental update based on your uploaded source document) ← only show this option when a source document was uploaded
+□ PDF document (professional layout with bookmark navigation, suitable for formal sharing)
+□ HTML planning report (interactive, suitable for online sharing)
+□ Word document (suitable for collaborative editing)
 □ PRD engineer delivery package (includes flowchart, DB schema, UI wireframe)
-□ PowerPoint presentation (suitable for meeting presentations)
+□ Presentation PPTX (suitable for meeting reports, recommend polishing with Keynote / PowerPoint after export)
 □ Dev handoff package (CLAUDE.md + TASKS.md + TICKETS.md + technical architecture — ready to start development in Claude Code)
 □ All of the above
 
-You can also say 'No thanks' to finish, or specify a particular document."
+You can also say 'No thanks' to finish, or specify a particular document.
+You can also use /export [pdf|docx|pptx|html|md] to export at any time."
 ```
 
 **Option display rules**:
+- Source document uploaded → "Updated [document type]" listed first with "(recommended)" label
 - Target audience is engineers → PRD and dev handoff package listed first
-- Target audience is executives/leadership → Presentation listed first
-- Target audience is cross-functional → Both HTML report and presentation listed
-- Quick Mode → Only ask if a presentation is needed
+- Target audience is executives/leadership → PDF and presentation listed first
+- Target audience is cross-functional → PDF, HTML report, and presentation all listed
+- Quick Mode → Only ask if PDF or presentation is needed
 - Target audience is yourself → Dev handoff package listed first
+
+**Export trigger rules**:
+- User selects PDF / Word / Presentation PPTX → Load `rules-export-document.md`
+- First time triggering document export → Load `rules-document-tools.md` first to check and install necessary tools
+- User selects HTML planning report → Load `06-html-report.md` (existing rules)
+- User selects "All of the above" → Execute each format export in sequence