@nahisaho/shikigami 1.47.0 → 1.49.0

package/AGENTS.md

@@ -40,7 +40,7 @@ VIOLATION = WORKFLOW FAILURE
 
 ---
 
-## Critical Rules (4 Absolute Prohibitions)
+## Critical Rules (5 Absolute Prohibitions)
 
 **⚠️ IMPORTANT: These rules MUST be followed. Violation breaks the research workflow.**
 
@@ -207,6 +207,36 @@ FORBIDDEN: Continuing without saving user input
 CONSEQUENCE: Conversation history will be lost if not saved
 ```
 
+### Prohibition 5: PDF Reference via Download and Text Conversion
+
+```
+WHEN: Referencing a PDF document in Deep Research
+DO:
+  1. Create research directory if not exists:
+     mkdir -p <project_path>/research
+  2. Download PDF using wget:
+     wget -O <project_path>/research/<filename>.pdf <pdf_url>
+  3. Convert PDF to text using pdftotext:
+     pdftotext <project_path>/research/<filename>.pdf <project_path>/research/<filename>.txt
+  4. Read and reference the converted text file
+  5. Save the extracted content via save_research
+
+EXAMPLE:
+  1. mkdir -p projects/pj00001_AIResearch/research
+  2. wget -O projects/pj00001_AIResearch/research/paper.pdf https://example.com/paper.pdf
+  3. pdftotext projects/pj00001_AIResearch/research/paper.pdf projects/pj00001_AIResearch/research/paper.txt
+  4. Read paper.txt and extract relevant information
+  5. save_research(content: <extracted_content>, source: "pdf", query: "paper.pdf")
+
+FORBIDDEN:
+  - Attempting to read PDF binary directly
+  - Skipping pdftotext conversion step
+  - Saving PDF to locations other than research directory
+  - Referencing PDF content without save_research
+
+CONSEQUENCE: PDF content will be unreadable or lost
+```
+
 ### Mandatory MCP Call Sequence
 
 Every search/visit operation MUST follow this pattern:
@@ -311,10 +341,11 @@ When user says "project created", "created project", or similar:
 2. **(Phase 0)** **Save Original Prompt** → `save_prompt(type: "original")`
 3. **(Phase 1)** **Prompt Optimization** → Structure into 6 elements → Display → **WAIT for user approval**
 4. **(Phase 2)** **Purpose Discovery** → Discover true purpose through 1Q1A dialogue
-5. **(Phase 3)** **Deep Research** → Think→Search→Report→Action cycle
-6. **(Phase 4)** **Framework Analysis** → Apply SWOT/3C/PEST etc.
-7. **(Phase 5)** **Report Generation** → Select template → Write report → Quality check → **WAIT for approval**
-8. **(Phase 6)** **Complete** → Update manifest.yaml, verify deliverables
+5. **(Phase 2.5)** **Knowledge Inheritance** → Search past projects → Inherit if relevant (optional)
+6. **(Phase 3)** **Deep Research** → Think→Search→Report→Action cycle
+7. **(Phase 4)** **Framework Analysis** → Apply SWOT/3C/PEST etc.
+8. **(Phase 5)** **Report Generation** → Select template → Write report → Quality check → **WAIT for approval**
+9. **(Phase 6)** **Complete** → Update manifest.yaml, verify deliverables
 
 ### Case B: New research request (no project yet)
 
@@ -327,10 +358,11 @@ When receiving a new research request:
 5. **(Phase 0)** **Verify Folder** → Confirm `projects/pjXXXXX_<Name>_YYYYMMDD/` exists
 6. **(Phase 1)** **Prompt Optimization** → Structure into 6 elements → Display → **WAIT for user approval**
 7. **(Phase 2)** **Purpose Discovery** → Discover true purpose through 1Q1A dialogue
-8. **(Phase 3)** **Deep Research** → Think→Search→Report→Action cycle
-9. **(Phase 4)** **Framework Analysis** → Apply SWOT/3C/PEST etc.
-10. **(Phase 5)** **Report Generation** → Select template → Write report → Quality check → **WAIT for approval**
-11. **(Phase 6)** **Complete** → Update manifest.yaml, verify deliverables
+8. **(Phase 2.5)** **Knowledge Inheritance** → Search past projects → Inherit if relevant (optional)
+9. **(Phase 3)** **Deep Research** → Think→Search→Report→Action cycle
+10. **(Phase 4)** **Framework Analysis** → Apply SWOT/3C/PEST etc.
+11. **(Phase 5)** **Report Generation** → Select template → Write report → Quality check → **WAIT for approval**
+12. **(Phase 6)** **Complete** → Update manifest.yaml, verify deliverables
 
 **MANDATORY APPROVAL POINTS** (must wait for user before proceeding):
 - Case B Step 1: Project name confirmation
@@ -455,6 +487,79 @@ OUTPUT: True purpose, research plan, search query list
 - CONSTRAINT: Time, budget, scope limitations?
 - SUCCESS: How do you define success?
 
+### Phase 2.5: Knowledge Inheritance (Optional)
+
+```
+WHEN: Phase 2 completed, before starting Phase 3
+DO:
+  1. Search past projects for related topics:
+     - Use semantic_search across all projects/*/research/ and projects/*/reports/
+     - Query: user's research topic + key concepts from Phase 2
+  2. If related projects found (similarity > 0.7):
+     - List related projects with summary
+     - Ask user: "関連する過去プロジェクトが見つかりました。継承しますか？"
+  3. If user approves inheritance:
+     - Create research/inherited/ directory
+     - Copy relevant files with source tracking
+     - Update manifest.yaml with inheritance info
+  4. Adjust Phase 3 research plan to focus on:
+     - Updates since last research (time-based delta)
+     - Gaps not covered in previous research
+     - New perspectives requested by user
+OUTPUT: Inherited knowledge list, adjusted research plan
+```
+
+**Related Project Display Format**:
+```markdown
+## 関連する過去プロジェクト
+
+| Project | Date | Topic | Similarity | Key Findings |
+|---------|------|-------|------------|-------------|
+| pj00001_AIMarket_20251015 | 2025-10-15 | AI市場調査 | 0.85 | 市場規橐500億円, 成長率15% |
+| pj00003_TechTrend_20251201 | 2025-12-01 | 技術トレンド | 0.72 | LLM採用率拡大 |
+
+継承しますか？ (はい/いいえ/選択して継承)
+```
+
+**Inheritance Directory Structure**:
+```
+projects/pjXXXXX_NewProject_YYYYMMDD/
+├── research/
+│   ├── inherited/                    # 継承ナレッジ
+│   │   ├── INHERITANCE_LOG.md        # 継承元追跡
+│   │   ├── pj00001_market-data.md    # 継承ファイル
+│   │   └── pj00003_tech-trends.md    # 継承ファイル
+│   └── search_*.md                   # 新規調査
+```
+
+**INHERITANCE_LOG.md Format**:
+```markdown
+# Knowledge Inheritance Log
+
+## Inherited From
+| Source Project | Files | Inherited Date | Reason |
+|----------------|-------|----------------|--------|
+| pj00001_AIMarket_20251015 | market-data.md | 2026-01-28 | 市場規模データの再利用 |
+
+## Delta Research Focus
+- [ ] 2025年10月以降の市場変化
+- [ ] 新規参入企業の動向
+- [ ] 規制環境の変化
+```
+
+**Delta Research Rules**:
+```
+WHEN: Knowledge inherited from past project
+DO:
+  1. Check publication dates of inherited data
+  2. Focus new searches on:
+     - Time period: [inherited_data_date] to [today]
+     - Query modifier: "2025年以降" or "latest" or "recent"
+  3. Compare new findings with inherited data
+  4. Mark changes with (Δ) in report:
+     - 市場規模: 500億円 → 580億円 (Δ+16%)
+```
+
 ### Phase 3: Deep Research
 
 ```
@@ -1024,4 +1129,4 @@ DO: Auto-detect Shift_JIS/EUC-JP/ISO-2022-JP and convert to UTF-8
 ---
 
 **Last Updated**: 2026-01-28  
-**Version**: 1.47.0
+**Version**: 1.48.0

package/CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to SHIKIGAMI will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.48.0] - 2026-01-28
+
+### Added
+
+- **AGENTS.md: Knowledge Inheritance (Phase 2.5)**
+  - New optional phase between Purpose Discovery and Deep Research
+  - Semantic search across past projects (research/ and reports/)
+  - Related project display with similarity scores
+  - User confirmation before inheritance
+  - `research/inherited/` directory structure
+  - `INHERITANCE_LOG.md` tracking format
+  - Delta Research Rules for time-based updates
+  - Change markers (Δ) for comparing inherited vs new data
+  - Workflow updated: Case A (8→9 steps), Case B (11→12 steps)
+
 ## [1.47.0] - 2026-01-28
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nahisaho/shikigami",
-  "version": "1.47.0",
+  "version": "1.49.0",
   "description": "GitHub Copilot Agent Skills for Deep Research & Consulting - AI-Powered Research Assistant with 50+ Consulting Frameworks",
   "keywords": [
     "github-copilot",