[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76S78K1ZJ092YYRKX0KBTYJ":3,"skill-same:01M76S78K1ZJ092YYRKX0KBTYJ":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M76S78K1ZJ092YYRKX0KBTYJ","litreview",null,"Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: litreview\ndescription: \"Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.\"\nlicense: MIT\nmetadata:\n  source_spec: \"megaprompts\u002F09-litreview-megaprompt.md\"\n  build_pattern: \"Path B (direct conversion)\"\n  research_pack_convention: \"Agent Integrity Rules verbatim per PR #657 audit; sibling of pulse\"\n  version: 1.0.0\n---\n\n# Litreview — Academic Literature Orientation\n\n> **Portability:** Requires a Consensus MCP connection, Node.js with `docx` package for document generation, and (in CLI) `bash_tool`. Works in Claude Code CLI natively. In Claude.ai with Consensus MCP + Code Execution, the workflow is supported.\n\nProduce a **launching pad** — not a finished literature review, but an orientation document that gives a researcher entering an unfamiliar field everything they need to start reading and searching with confidence. Think: what a generous colleague who knows the field would tell you over coffee.\n\n## Agent Integrity Rules (Research-Pack Convention)\n\nInherited from the research-pack convention; locked verbatim per PR #657's cross-skill consistency audit.\n\n- **Source discipline.** Only cite Consensus-returned papers from THIS session. Training knowledge labeled `[Not from Consensus — model knowledge]` and excluded from cited count. Sparse results stated explicitly, never silently filled.\n- **Counting discipline.** Three numbers tracked: searches executed \u002F unique papers received (deduplicated) \u002F papers cited. Every cited paper has a retrievable Consensus URL from this session. Use `scripts\u002Fcitation_tracker.py` for deterministic counts.\n- **Tool constraints.** Consensus per-query cap depends on plan tier. **Detect at first search**, report at checkpoint. Rate limit is **1 query\u002Fsec** — sequential execution mandatory.\n- **Retry policy.** On failure → wait 3s → retry once → log. After 3 consecutive failures: stop, alert user, share what was collected.\n- **Plan-tier detection.** Parse first-search response for \"Showing top 10\" \u002F \"upgrade\" → free tier (10\u002Fsearch). 20 returned → Pro (20\u002Fsearch). Calculate theoretical ceiling and surface at checkpoint so user can recalibrate.\n\nSee [`references\u002Fsearch_budget_allocation.md`](references\u002Fsearch_budget_allocation.md) for the sequential-execution rationale + plan-tier signals.\n\n## Error Handling\n\n| Failure | Behavior |\n|---|---|\n| Consensus rate-limit hit | Wait 3s, retry once, log outcome |\n| Search returns 0 results | Note explicitly; \"either niche terminology or genuine gap\"; never silently fill |\n| Plan-tier cap detected | Log tier; report at checkpoint; surface in audit |\n| 3 consecutive failures | Stop searching, alert user, share what's collected, ask how to proceed |\n| Sub-area returns thin results (\u003C5 papers) | Flag in audit; suggest manual PubMed\u002FScholar supplementation |\n| User wants to adjust sub-areas | Update table, re-confirm before searching |\n| DOCX validation fails | Unpack XML, fix, repack |\n\n## Phase 0: Grill-Me Intake (3 forcing questions, one at a time)\n\nEach question carries explicit \"why I'm asking\". Stop condition: max 3 before Phase 1.\n\n### Q1 (root) — Research question specificity\n\n> **State the research question in 1–2 sentences. Specific is better — \"How do LLMs perform on clinical reasoning tasks compared to physicians?\" beats \"AI in medicine\". Vague questions produce vague reviews.**\n>\n> *Why I'm asking:* The reconnaissance search hinges on precise terminology. Vague questions produce thin recon results that don't yield a useful framework breakdown.\n\n**Refuse mush.** Re-ask once with examples if user is too broad. If still vague, deliver with explicit \"broad-scope orientation, not depth review\" caveat.\n\n### Q2 (depends on Q1) — Framework hint\n\n> **Framework — pick one or say \"you pick\":**\n>\n> 1. **PICO** (Population \u002F Intervention \u002F Comparison \u002F Outcome — most clinical questions)\n> 2. **SPIDER** (Sample \u002F Phenomenon \u002F Design \u002F Evaluation \u002F Research-type — social\u002Fqualitative)\n> 3. **Decomposition** (Problem \u002F Solution \u002F Evaluation \u002F Limitations — technology-focused)\n> 4. **Hybrid** (you pick which components from which framework)\n> 5. **You pick** — analyze Q1 and recommend\n>\n> *Why I'm asking:* PICO is the default for ~70% of clinical questions but maps poorly to qualitative work or technology evaluation. Picking upfront saves the recon search from suggesting a misaligned framework.\n\nForcing choice with default (\"you pick\"). The skill surfaces its own framework recommendation after the recon search so user can override. Use `scripts\u002Fframework_recommender.py` for the heuristic.\n\nSee [`references\u002Fframework_selection.md`](references\u002Fframework_selection.md) for PICO \u002F SPIDER \u002F Decomposition canon.\n\n### Q3 (depends on Q1) — Tentative depth\n\n> **Tentative depth — pick one. Final confirmation comes after the framework breakdown:**\n>\n> 1. **Quick scan** (5 searches)\n> 2. **Standard review** (10 searches)\n> 3. **Deep dive** (20 searches)\n>\n> *Why I'm asking:* I ask this twice — once now to calibrate the recon search emphasis, once after the framework breakdown to confirm. Tentative answer affects which sub-areas to surface first; final answer drives search budget allocation.\n\nForcing choice. **Re-asked** at the post-Phase-2 checkpoint after the user has seen the framework breakdown.\n\n**Stop condition:** 3 questions max before Phase 1. The post-Phase-2 checkpoint is its own grill-me moment (framework table + sub-area-adjustment + depth-reconfirmation).\n\n## Phase 1: Initial Reconnaissance\n\n**One broad Consensus search** to map themes, terminology, methodological distinctions.\n\n- Query: broad version of Q1 (terminology variants are okay; first search casts wide)\n- Record: `citation_tracker.py --action record_search --session NAME --query \"...\"`\n- Record received count: `citation_tracker.py --action record_papers_received --session NAME --count N`\n- **Detect plan tier** from response: \"Showing top 10\" \u002F \"upgrade\" → free; 20 returned → Pro\n\nSynthesize for the checkpoint:\n- Themes that surfaced\n- Terminology variations (e.g., \"LLM\" vs \"large language model\" vs \"GPT-style model\")\n- Methodological distinctions (clinical trials vs benchmark eval vs case study)\n- Coverage gaps (sub-questions absent from recon results)\n\n## Phase 2: Framework Selection + Sub-area Generation\n\nChoose framework (from Q2 OR override based on recon):\n- **PICO** — most clinical questions (~70% default)\n- **SPIDER** — social \u002F qualitative\n- **Decomposition** — technology focus (Problem \u002F Solution \u002F Evaluation \u002F Limitations)\n- **Hybrid** — explicit cross-framework mapping\n\nGenerate **4-5 sub-area questions** mapped to framework components. Each becomes a targeted Phase 3 search.\n\n## Checkpoint (grill-me forcing-options moment)\n\nAfter Phase 2, halt and present:\n\n### 3-4 sentence recon summary\n- What themes surfaced\n- Terminology landscape\n- Evidence landscape characterization\n\n### Framework breakdown table\n\n| Framework Component | How It Maps to This Topic | Proposed Sub-area to Explore |\n|---|---|---|\n| (Component 1) | ... | Sub-area 1 |\n| (Component 2) | ... | Sub-area 2 |\n| (Component 3) | ... | Sub-area 3 |\n| (Component 4) | ... | Sub-area 4 |\n| Cross-cutting theme | ... | Sub-area 5 |\n\n### Depth re-confirmation (forcing choice)\n\nSurface the **practical constraint**: detected plan tier + theoretical ceiling.\n\n- Quick scan (5 searches × ~10 results each = ~50 papers max)\n- Standard review (10 searches × ~10 = ~100 papers)\n- Deep dive (20 searches × ~10 = ~200 papers)\n\n### Sub-area forcing options\n\n- \"Looks good — proceed with these sub-areas\"\n- \"Adjust: add sub-area on [X]\"\n- \"Adjust: remove and replace [Y] with [Z]\"\n- \"Restart with different framework\"\n\n### Why I'm asking (the rationale)\n\n> A wrong framework or sub-area set wastes the search budget. This is the **last cheap moment** to correct course.\n\n**Wait for user response before Phase 3.** Refuse to start Phase 3 without explicit user choice.\n\n## Phase 3: Targeted Searches\n\nSequential (1 query\u002Fsec), budget per depth tier. See [`references\u002Fsearch_budget_allocation.md`](references\u002Fsearch_budget_allocation.md) for full canon.\n\n### Quick scan (5 searches)\n- 5 sub-area searches (one per sub-area)\n- Skip era-gated + review-specific\n\n### Standard review (10 searches)\n- 5 sub-area searches\n- 2 review article searches (top 2 sub-areas): `\"systematic review [topic]\"` \u002F `\"meta-analysis [topic]\"`\n- 2 era-gated searches (most important sub-area): `year_max: 2015` + `year_min: 2021`\n- 1 follow-up on highest-cited paper using its key terms + `year_min` after publication\n\n### Deep dive (20 searches)\n- 5 sub-area searches\n- 5 review article searches (one per sub-area)\n- 4 era-gated searches (top 2 sub-areas, old + new each)\n- 3 follow-ups on top 3 highest-cited papers\n- 3 spare for emerging threads (surprising findings to chase)\n\nThroughout: 1 q\u002Fsec rate limit. Sequential. Confirm response before next call. Record each via `citation_tracker.py`.\n\n## Cross-Search Intelligence\n\nThree trackers across ALL search results — run `scripts\u002Fcross_search_aggregator.py --session NAME` after Phase 3 completes:\n\n1. **Repeat-hit papers** — same paper appearing in 3+ sub-area searches = likely foundational\n2. **Recurring authors** — same author in multiple searches = dominant research group; top 3-5 most frequent matter\n3. **Citation-per-year heuristic** — a 2023 paper with 150 citations >> 2008 paper with 150 citations. Use for seminal-work identification.\n\nThese feed the \"Start Here\" + \"Key Research Groups\" + \"Bibliography\" DOCX sections.\n\n## Phase 4: DOCX Research Guide\n\nGenerate via Node.js + `docx` library. 8 sections (see [`references\u002Fdocx_8_sections.md`](references\u002Fdocx_8_sections.md) for full spec):\n\n1. **Topic Overview** — single tight paragraph (4-6 sentences)\n2. **Start Here — Priority Reading Order** — 5-7 papers ordered: best recent review → foundational → 2-3 frontier → gap\u002Fcontroversy. Each: hyperlinked title + authors\u002Fyear + 1-sentence contribution + 1-sentence \"what to look for\"\n3. **How the Field Got Here** — chronological narrative (1-2 paragraphs) + timeline table (5-8 milestones: Year \u002F Milestone \u002F Significance) + terminology evolution note\n4. **Sub-area Guides** (one per sub-area, 4 parts each)\n   - 4a. What the Research Shows (2-3 sentence synthesis with inline citations)\n   - 4b. Key Papers (3-5 hyperlinked papers with citation count, year, 1-sentence importance)\n   - 4c. Key Search Terms (6-10 keywords, synonyms, MeSH, historical terms)\n   - 4d. Boolean Search Strings (2-3 ready-to-paste strings)\n5. **Key Research Groups** — top 3-5 authors\u002Fgroups with affiliations, sub-area coverage, representative paper link (from cross-search aggregator)\n6. **Open Questions & Gaps** — three categories: methodological \u002F population-context \u002F conceptual-theoretical. Each gap explains *why it matters*.\n7. **Bibliography** — alphabetical by first author. Every entry has clickable \"View on Consensus\" link. Every inline citation matches a bibliography entry.\n8. **Audit Log** — search summary table (#, query, filters, papers returned, status), counts block, coverage notes including detected tier and theoretical ceiling\n\n### DOCX Technical Requirements\n\nDocument the key `docx` library patterns:\n\n- Page: US Letter, 1-inch margins\n- Lists: `LevelFormat.BULLET` (never unicode bullets)\n- Hyperlinks: `ExternalHyperlink` with `style: \"Hyperlink\"`, full URL (never truncated)\n- Tables: dual widths (`columnWidths` + cell `width`), `ShadingType.CLEAR`\n- Validation step after save (`python scripts\u002Foffice\u002Fvalidate.py output.docx`)\n\nReference the **docx skill** for setup patterns and best practices.\n\n## Output\n\n```\nresearch_guide_\u003Ctopic-slug>_\u003CYYYY-MM-DD>.docx\n```\n\nPlus:\n- Chat summary block: \"Saved: \u003Cpath>. Audit: N searches × M unique papers \u002F K cited. Plan tier: \u003Ctier>.\"\n- Audit log printed inline if user asks for it\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fcitation_tracker.py` | JSON-backed three-count audit at `~\u002F.litreview_sessions\u002F\u003Csession>.json` |\n| `scripts\u002Fframework_recommender.py` | Heuristic PICO\u002FSPIDER\u002FDecomposition suggestion from research question |\n| `scripts\u002Fcross_search_aggregator.py` | Repeat-hits + recurring-authors + citation-per-year ranking after Phase 3 |\n\n## References\n\n- [`references\u002Fframework_selection.md`](references\u002Fframework_selection.md) — PICO \u002F SPIDER \u002F Decomposition canon (7+ sources)\n- [`references\u002Fsearch_budget_allocation.md`](references\u002Fsearch_budget_allocation.md) — depth tiers + cross-search intelligence + sequential execution rationale (7+ sources)\n- [`references\u002Fdocx_8_sections.md`](references\u002Fdocx_8_sections.md) — research guide DOCX spec + technical requirements (7+ sources)\n\n## Anti-Patterns To Reject\n\n- Parallelizing Consensus calls\n- Skipping the interactive checkpoint (running all searches without user confirmation)\n- Padding thin results with training knowledge\n- Defaulting to non-PICO framework without justification\n- Citing papers in chat that didn't come from Consensus this session\n- Hardcoding plan tier instead of detecting from first response\n- Skipping era-gated searches in standard\u002Fdeep budgets\n- Skipping cross-search intelligence (repeat-hits, recurring authors)\n- Truncating Consensus URLs in hyperlinks\n\n---\n\n**Version:** 1.0.0\n**Source spec:** [`megaprompts\u002F09-litreview-megaprompt.md`](..\u002F..\u002F..\u002F..\u002Fmegaprompts\u002F09-litreview-megaprompt.md)\n**Build pattern:** Path B (direct conversion). Sibling of `pulse` (research-pack shape).\n","# Litreview — Academic Literature Orientation\n\n> **Portability:** Requires a Consensus MCP connection, Node.js with `docx` package for document generation, and (in CLI) `bash_tool`. Works in Claude Code CLI natively. In Claude.ai with Consensus MCP + Code Execution, the workflow is supported.\n\nProduce a **launching pad** — not a finished literature review, but an orientation document that gives a researcher entering an unfamiliar field everything they need to start reading and searching with confidence. Think: what a generous colleague who knows the field would tell you over coffee.\n\n## Agent Integrity Rules (Research-Pack Convention)\n\nInherited from the research-pack convention; locked verbatim per PR #657's cross-skill consistency audit.\n\n- **Source discipline.** Only cite Consensus-returned papers from THIS session. Training knowledge labeled `[Not from Consensus — model knowledge]` and excluded from cited count. Sparse results stated explicitly, never silently filled.\n- **Counting discipline.** Three numbers tracked: searches executed \u002F unique papers received (deduplicated) \u002F papers cited. Every cited paper has a retrievable Consensus URL from this session. Use `scripts\u002Fcitation_tracker.py` for deterministic counts.\n- **Tool constraints.** Consensus per-query cap depends on plan tier. **Detect at first search**, report at checkpoint. Rate limit is **1 query\u002Fsec** — sequential execution mandatory.\n- **Retry policy.** On failure → wait 3s → retry once → log. After 3 consecutive failures: stop, alert user, share what was collected.\n- **Plan-tier detection.** Parse first-search response for \"Showing top 10\" \u002F \"upgrade\" → free tier (10\u002Fsearch). 20 returned → Pro (20\u002Fsearch). Calculate theoretical ceiling and surface at checkpoint so user can recalibrate.\n\nSee [`references\u002Fsearch_budget_allocation.md`](references\u002Fsearch_budget_allocation.md) for the sequential-execution rationale + plan-tier signals.\n\n## Error Handling\n\n| Failure | Behavior |\n|---|---|\n| Consensus rate-limit hit | Wait 3s, retry once, log outcome |\n| Search returns 0 results | Note explicitly; \"either niche terminology or genuine gap\"; never silently fill |\n| Plan-tier cap detected | Log tier; report at checkpoint; surface in audit |\n| 3 consecutive failures | Stop searching, alert user, share what's collected, ask how to proceed |\n| Sub-area returns thin results (\u003C5 papers) | Flag in audit; suggest manual PubMed\u002FScholar supplementation |\n| User wants to adjust sub-areas | Update table, re-confirm before searching |\n| DOCX validation fails | Unpack XML, fix, repack |\n\n## Phase 0: Grill-Me Intake (3 forcing questions, one at a time)\n\nEach question carries explicit \"why I'm asking\". Stop condition: max 3 before Phase 1.\n\n### Q1 (root) — Research question specificity\n\n> **State the research question in 1–2 sentences. Specific is better — \"How do LLMs perform on clinical reasoning tasks compared to physicians?\" beats \"AI in medicine\". Vague questions produce vague reviews.**\n>\n> *Why I'm asking:* The reconnaissance search hinges on precise terminology. Vague questions produce thin recon results that don't yield a useful framework breakdown.\n\n**Refuse mush.** Re-ask once with examples if user is too broad. If still vague, deliver with explicit \"broad-scope orientation, not depth review\" caveat.\n\n### Q2 (depends on Q1) — Framework hint\n\n> **Framework — pick one or say \"you pick\":**\n>\n> 1. **PICO** (Population \u002F Intervention \u002F Comparison \u002F Outcome — most clinical questions)\n> 2. **SPIDER** (Sample \u002F Phenomenon \u002F Design \u002F Evaluation \u002F Research-type — social\u002Fqualitative)\n> 3. **Decomposition** (Problem \u002F Solution \u002F Evaluation \u002F Limitations — technology-focused)\n> 4. **Hybrid** (you pick which components from which framework)\n> 5. **You pick** — analyze Q1 and recommend\n>\n> *Why I'm asking:* PICO is the default for ~70% of clinical questions but maps poorly to qualitative work or technology evaluation. Picking upfront saves the recon search from suggesting a misaligned framework.\n\nForcing choice with default (\"you pick\"). The skill surfaces its own framework recommendation after the recon search so user can override. Use `scripts\u002Fframework_recommender.py` for the heuristic.\n\nSee [`references\u002Fframework_selection.md`](references\u002Fframework_selection.md) for PICO \u002F SPIDER \u002F Decomposition canon.\n\n### Q3 (depends on Q1) — Tentative depth\n\n> **Tentative depth — pick one. Final confirmation comes after the framework breakdown:**\n>\n> 1. **Quick scan** (5 searches)\n> 2. **Standard review** (10 searches)\n> 3. **Deep dive** (20 searches)\n>\n> *Why I'm asking:* I ask this twice — once now to calibrate the recon search emphasis, once after the framework breakdown to confirm. Tentative answer affects which sub-areas to surface first; final answer drives search budget allocation.\n\nForcing choice. **Re-asked** at the post-Phase-2 checkpoint after the user has seen the framework breakdown.\n\n**Stop condition:** 3 questions max before Phase 1. The post-Phase-2 checkpoint is its own grill-me moment (framework table + sub-area-adjustment + depth-reconfirmation).\n\n## Phase 1: Initial Reconnaissance\n\n**One broad Consensus search** to map themes, terminology, methodological distinctions.\n\n- Query: broad version of Q1 (terminology variants are okay; first search casts wide)\n- Record: `citation_tracker.py --action record_search --session NAME --query \"...\"`\n- Record received count: `citation_tracker.py --action record_papers_received --session NAME --count N`\n- **Detect plan tier** from response: \"Showing top 10\" \u002F \"upgrade\" → free; 20 returned → Pro\n\nSynthesize for the checkpoint:\n- Themes that surfaced\n- Terminology variations (e.g., \"LLM\" vs \"large language model\" vs \"GPT-style model\")\n- Methodological distinctions (clinical trials vs benchmark eval vs case study)\n- Coverage gaps (sub-questions absent from recon results)\n\n## Phase 2: Framework Selection + Sub-area Generation\n\nChoose framework (from Q2 OR override based on recon):\n- **PICO** — most clinical questions (~70% default)\n- **SPIDER** — social \u002F qualitative\n- **Decomposition** — technology focus (Problem \u002F Solution \u002F Evaluation \u002F Limitations)\n- **Hybrid** — explicit cross-framework mapping\n\nGenerate **4-5 sub-area questions** mapped to framework components. Each becomes a targeted Phase 3 search.\n\n## Checkpoint (grill-me forcing-options moment)\n\nAfter Phase 2, halt and present:\n\n### 3-4 sentence recon summary\n- What themes surfaced\n- Terminology landscape\n- Evidence landscape characterization\n\n### Framework breakdown table\n\n| Framework Component | How It Maps to This Topic | Proposed Sub-area to Explore |\n|---|---|---|\n| (Component 1) | ... | Sub-area 1 |\n| (Component 2) | ... | Sub-area 2 |\n| (Component 3) | ... | Sub-area 3 |\n| (Component 4) | ... | Sub-area 4 |\n| Cross-cutting theme | ... | Sub-area 5 |\n\n### Depth re-confirmation (forcing choice)\n\nSurface the **practical constraint**: detected plan tier + theoretical ceiling.\n\n- Quick scan (5 searches × ~10 results each = ~50 papers max)\n- Standard review (10 searches × ~10 = ~100 papers)\n- Deep dive (20 searches × ~10 = ~200 papers)\n\n### Sub-area forcing options\n\n- \"Looks good — proceed with these sub-areas\"\n- \"Adjust: add sub-area on [X]\"\n- \"Adjust: remove and replace [Y] with [Z]\"\n- \"Restart with different framework\"\n\n### Why I'm asking (the rationale)\n\n> A wrong framework or sub-area set wastes the search budget. This is the **last cheap moment** to correct course.\n\n**Wait for user response before Phase 3.** Refuse to start Phase 3 without explicit user choice.\n\n## Phase 3: Targeted Searches\n\nSequential (1 query\u002Fsec), budget per depth tier. See [`references\u002Fsearch_budget_allocation.md`](references\u002Fsearch_budget_allocation.md) for full canon.\n\n### Quick scan (5 searches)\n- 5 sub-area searches (one per sub-area)\n- Skip era-gated + review-specific\n\n### Standard review (10 searches)\n- 5 sub-area searches\n- 2 review article searches (top 2 sub-areas): `\"systematic review [topic]\"` \u002F `\"meta-analysis [topic]\"`\n- 2 era-gated searches (most important sub-area): `year_max: 2015` + `year_min: 2021`\n- 1 follow-up on highest-cited paper using its key terms + `year_min` after publication\n\n### Deep dive (20 searches)\n- 5 sub-area searches\n- 5 review article searches (one per sub-area)\n- 4 era-gated searches (top 2 sub-areas, old + new each)\n- 3 follow-ups on top 3 highest-cited papers\n- 3 spare for emerging threads (surprising findings to chase)\n\nThroughout: 1 q\u002Fsec rate limit. Sequential. Confirm response before next call. Record each via `citation_tracker.py`.\n\n## Cross-Search Intelligence\n\nThree trackers across ALL search results — run `scripts\u002Fcross_search_aggregator.py --session NAME` after Phase 3 completes:\n\n1. **Repeat-hit papers** — same paper appearing in 3+ sub-area searches = likely foundational\n2. **Recurring authors** — same author in multiple searches = dominant research group; top 3-5 most frequent matter\n3. **Citation-per-year heuristic** — a 2023 paper with 150 citations >> 2008 paper with 150 citations. Use for seminal-work identification.\n\nThese feed the \"Start Here\" + \"Key Research Groups\" + \"Bibliography\" DOCX sections.\n\n## Phase 4: DOCX Research Guide\n\nGenerate via Node.js + `docx` library. 8 sections (see [`references\u002Fdocx_8_sections.md`](references\u002Fdocx_8_sections.md) for full spec):\n\n1. **Topic Overview** — single tight paragraph (4-6 sentences)\n2. **Start Here — Priority Reading Order** — 5-7 papers ordered: best recent review → foundational → 2-3 frontier → gap\u002Fcontroversy. Each: hyperlinked title + authors\u002Fyear + 1-sentence contribution + 1-sentence \"what to look for\"\n3. **How the Field Got Here** — chronological narrative (1-2 paragraphs) + timeline table (5-8 milestones: Year \u002F Milestone \u002F Significance) + terminology evolution note\n4. **Sub-area Guides** (one per sub-area, 4 parts each)\n   - 4a. What the Research Shows (2-3 sentence synthesis with inline citations)\n   - 4b. Key Papers (3-5 hyperlinked papers with citation count, year, 1-sentence importance)\n   - 4c. Key Search Terms (6-10 keywords, synonyms, MeSH, historical terms)\n   - 4d. Boolean Search Strings (2-3 ready-to-paste strings)\n5. **Key Research Groups** — top 3-5 authors\u002Fgroups with affiliations, sub-area coverage, representative paper link (from cross-search aggregator)\n6. **Open Questions & Gaps** — three categories: methodological \u002F population-context \u002F conceptual-theoretical. Each gap explains *why it matters*.\n7. **Bibliography** — alphabetical by first author. Every entry has clickable \"View on Consensus\" link. Every inline citation matches a bibliography entry.\n8. **Audit Log** — search summary table (#, query, filters, papers returned, status), counts block, coverage notes including detected tier and theoretical ceiling\n\n### DOCX Technical Requirements\n\nDocument the key `docx` library patterns:\n\n- Page: US Letter, 1-inch margins\n- Lists: `LevelFormat.BULLET` (never unicode bullets)\n- Hyperlinks: `ExternalHyperlink` with `style: \"Hyperlink\"`, full URL (never truncated)\n- Tables: dual widths (`columnWidths` + cell `width`), `ShadingType.CLEAR`\n- Validation step after save (`python scripts\u002Foffice\u002Fvalidate.py output.docx`)\n\nReference the **docx skill** for setup patterns and best practices.\n\n## Output\n\n```\nresearch_guide_\u003Ctopic-slug>_\u003CYYYY-MM-DD>.docx\n```\n\nPlus:\n- Chat summary block: \"Saved: \u003Cpath>. Audit: N searches × M unique papers \u002F K cited. Plan tier: \u003Ctier>.\"\n- Audit log printed inline if user asks for it\n\n## Tooling\n\n| Script | Role |\n|---|---|\n| `scripts\u002Fcitation_tracker.py` | JSON-backed three-count audit at `~\u002F.litreview_sessions\u002F\u003Csession>.json` |\n| `scripts\u002Fframework_recommender.py` | Heuristic PICO\u002FSPIDER\u002FDecomposition suggestion from research question |\n| `scripts\u002Fcross_search_aggregator.py` | Repeat-hits + recurring-authors + citation-per-year ranking after Phase 3 |\n\n## References\n\n- [`references\u002Fframework_selection.md`](references\u002Fframework_selection.md) — PICO \u002F SPIDER \u002F Decomposition canon (7+ sources)\n- [`references\u002Fsearch_budget_allocation.md`](references\u002Fsearch_budget_allocation.md) — depth tiers + cross-search intelligence + sequential execution rationale (7+ sources)\n- [`references\u002Fdocx_8_sections.md`](references\u002Fdocx_8_sections.md) — research guide DOCX spec + technical requirements (7+ sources)\n\n## Anti-Patterns To Reject\n\n- Parallelizing Consensus calls\n- Skipping the interactive checkpoint (running all searches without user confirmation)\n- Padding thin results with training knowledge\n- Defaulting to non-PICO framework without justification\n- Citing papers in chat that didn't come from Consensus this session\n- Hardcoding plan tier instead of detecting from first response\n- Skipping era-gated searches in standard\u002Fdeep budgets\n- Skipping cross-search intelligence (repeat-hits, recurring authors)\n- Truncating Consensus URLs in hyperlinks\n\n---\n\n**Version:** 1.0.0\n**Source spec:** [`megaprompts\u002F09-litreview-megaprompt.md`](..\u002F..\u002F..\u002F..\u002Fmegaprompts\u002F09-litreview-megaprompt.md)\n**Build pattern:** Path B (direct conversion). Sibling of `pulse` (research-pack shape).\n",{"name":5,"license":14,"metadata":23,"description":7},{"version":24,"source_spec":25,"build_pattern":26,"research_pack_convention":27},"1.0.0","megaprompts\u002F09-litreview-megaprompt.md","Path B (direct conversion)","Agent Integrity Rules verbatim per PR #657 audit; sibling of pulse","main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","research\u002Flitreview\u002Fskills\u002Flitreview","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add msm47\u002FGitskil --skill litreview",{"tool":40,"command":41},"bunx","bunx skills add msm47\u002FGitskil --skill litreview",{"tool":43,"command":44},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill litreview","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",true,[48,54,58,62,68,72],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdocx_8_sections.md","REFERENCE","参考文档",11835,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002Freferences\u002Fdocx_8_sections.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fframework_selection.md",9235,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002Freferences\u002Fframework_selection.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fsearch_budget_allocation.md",9744,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002Freferences\u002Fsearch_budget_allocation.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Fcitation_tracker.py","SCRIPT","脚本",10264,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002Fscripts\u002Fcitation_tracker.py",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fcross_search_aggregator.py",9910,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002Fscripts\u002Fcross_search_aggregator.py",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fframework_recommender.py",9199,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002Fscripts\u002Fframework_recommender.py",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M76S8VB9Q65XVZXC99QVF20M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M76S8K8X17M3CV7RENS6KA32","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M76S8AZCNS7Q5M4G1SBQ8HDV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M76S7YVS0NHD51AFTZM5965R","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M76S7MQDZR49Y3DRXF394R2F","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M76S70CRXWVJCQWGZ49AYCE0","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Triggers: 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research', or any grant-related request. NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]