zrwangems/dsh-zrwang-plugin / ars/skills/academic-pipeline
academic-pipeline
Flagged学术研究总编排:研究→写作→诚信检查→评审→返修→复审→终检→定稿的十阶段流水线,每阶段停在用户确认点,含材料护照与 7 类 AI 研究失败模式检查。Triggers: academic pipeline, research to paper, full paper workflow, end-to-end paper | 完整论文流程, 从研究到论文, 端到端写论文, 论文流水线。
references/mode_advisor.md
View on GitHub> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Mode Advisor — Unified Cross-Skill Decision Tree
## Purpose
Helps users (and the pipeline orchestrator) select the right skill and mode for their current situation. Eliminates the most common routing mistakes by mapping user intent to the optimal entry point.
---
## Quick Decision Matrix
| What do you want? | How far along? | Time? | Skill + Mode |
|-------------------|---------------|-------|--------------|
| Explore a topic | Starting fresh | 30 min | deep-research quick |
| Explore a topic | Starting fresh | 2+ hr | deep-research full |
| Think through a research idea | Have vague idea | Any | deep-research socratic |
| Systematic review | Have clear PICO | 3+ hr | deep-research systematic-review |
| Verify claims | Have specific claims | 30 min | deep-research fact-check |
| Write a paper | Have research done | 2+ hr | academic-paper full |
| Plan a paper step by step | Have RQ, need structure | 1+ hr | academic-paper plan |
| Fix citations | Have draft | 30 min | academic-paper citation-check |
| Convert format | Have final draft | 15 min | academic-paper format-convert |
| Review a paper | Have paper to evaluate | 1 hr | academic-paper-reviewer full |
| Check revision quality | Have revised draft | 30 min | academic-paper-reviewer re-review |
| Full pipeline (zero to publication) | Starting fresh | 5+ hr | academic-pipeline |
| Handle real reviewer feedback | Have review comments | 1+ hr | academic-pipeline (Stage 4 entry) |
---
## Common Misconceptions
| User Says | They Probably Need | Why |
|-----------|-------------------|-----|
| "Write me a paper on X" | deep-research first, THEN academic-paper | Writing without research produces shallow papers with unsupported claims |
| "Review my paper" (but no draft exists) | academic-paper plan mode | They need to write first, not review |
| "Check my citations" (but paper isn't done) | academic-paper full mode | Finish writing first, then check citations as a separate pass |
| "I need a systematic review" | deep-research systematic-review mode | NOT academic-paper lit-review structure (different methodology: PRISMA vs narrative) |
| "Just give me a quick paper" | deep-research quick + academic-paper full | Quick research is fine, but paper writing still needs the full mode for quality |
| "Format my paper as APA" | academic-paper format-convert mode | Not a rewrite; purely formatting transformation |
| "I got reviewer comments" | academic-pipeline Stage 4 entry (External Review) | Needs structured intake + strategic coaching, not just "fix what they said" |
---
## User Archetype Recommendations
| Archetype | Recommended Workflow | Rationale |
|-----------|---------------------|-----------|
| Graduate student (first paper) | deep-research socratic -> academic-paper plan -> full pipeline | Socratic mode builds research thinking; plan mode structures the paper incrementally; pipeline ensures quality gates |
| Experienced researcher (submission prep) | academic-pipeline (full, from Stage 1 or mid-entry) | Knows what they want; benefits from the automated quality assurance and integrity checks |
| Advisor reviewing student work | academic-paper-reviewer full | Provides structured multi-perspective feedback the advisor can use in mentoring |
| Quick literature scan | deep-research quick or lit-review | Fast turnaround; no need for full pipeline overhead |
| Journal revision response | academic-pipeline (Stage 4 entry with review comments) | External Review Protocol handles real reviewer feedback with strategic coaching |
| Conference paper (short deadline) | deep-research quick -> academic-paper full (conference type) | Compressed timeline; quick research + full writing with conference structure |
| Thesis chapter | deep-research full -> academic-paper full | Each chapter treated as a standalone paper; full depth needed |
| Policy brief | deep-research quick -> academic-paper full (policy_brief type) | Evidence-based but concise; quick research sufficient for policy scope |
---
## Skill Capability Boundaries
Understanding what each skill can and cannot do prevents misrouting:
| Skill | Can Do | Cannot Do |
|-------|--------|-----------|
| deep-research | Literature search, synthesis, RQ refinement, fact-checking | Write papers, review papers, format documents |
| academic-paper | Write papers, revise papers, format documents, check citations | Conduct original research, review papers (as reviewer), verify integrity |
| academic-paper-reviewer | Review papers (5-person panel), re-review revisions | Write papers, conduct research, fix issues (only identifies them) |
| academic-pipeline | Orchestrate all stages, manage transitions, track state | Perform any substantive work (purely dispatching and coordinating) |
| integrity_verification_agent | Verify references, citations, data, originality | Fix issues (only identifies them), review paper quality |
---
## Decision Flowchart
```
START: What does the user want?
|
+--> "I want to research/explore/investigate"
| |
| +--> Have specific claims to verify? --> deep-research fact-check
| +--> Have clear PICO/systematic question? --> deep-research systematic-review
| +--> Want guided exploration? --> deep-research socratic
| +--> Want direct results, have time? --> deep-research full
| +--> Want direct results, short on time? --> deep-research quick
|
+--> "I want to write a paper"
| |
| +--> Have research/literature ready? --> academic-paper (plan or full)
| +--> No research done yet? --> deep-research FIRST, then academic-paper
| +--> Want full quality assurance? --> academic-pipeline (from Stage 1)
|
+--> "I want someone to review my paper"
| |
| +--> Have a complete draft? --> academic-paper-reviewer full
| +--> Want integrity check + review? --> academic-pipeline (Stage 2.5 entry)
| +--> No draft yet? --> academic-paper first
|
+--> "I need to revise based on feedback"
| |
| +--> From AI reviewers (pipeline)? --> Continue pipeline (Stage 4)
| +--> From real journal reviewers? --> academic-pipeline Stage 4 entry (External Review)
|
+--> "I want the full treatment (research to publication)"
|
+--> academic-pipeline (Stage 1 entry)
```
---
## Pipeline Stage Entry Points
For users entering the pipeline mid-stream, this table clarifies what materials are needed:
| Entry Point | Required Materials | What Gets Skipped | Integrity Implications |
|------------|-------------------|-------------------|----------------------|
| Stage 1 (RESEARCH) | None | Nothing | Full pipeline |
| Stage 2 (WRITE) | RQ Brief + Bibliography | Stage 1 | Full pipeline from Stage 2 |
| Stage 2.5 (INTEGRITY) | Paper draft | Stages 1-2 | Integrity check runs on provided draft |
| Stage 3 (REVIEW) | Paper draft (a prior integrity report is optional context) | Stages 1-2 | Stage 2.5 runs first on the provided paper; a prior report informs it but does not replace it |
| Stage 4 (REVISE) | Paper + review comments | Stages 1-3 | Pipeline runs Stage 4 -> 3' -> 4.5 -> 5; Stage 4' runs between 3' and 4.5 only after a Major decision |
| Stage 5 (FINALIZE) | Revised paper (a prior integrity report is optional context) | Stages 1-4 | Stage 4.5 runs first on the provided paper; a prior report informs it but does not replace it |
---
## Anti-Patterns
These are common workflow mistakes to avoid:
| Anti-Pattern | Problem | Correct Approach |
|-------------|---------|-----------------|
| Skipping research | Paper lacks evidence depth | Always do at least deep-research quick |
| Writing then researching | Confirmation bias in source selection | Research first, write second |
| Reviewing before integrity check | Wasted review effort on fabricated citations | Always Stage 2.5 before Stage 3 |
| Accepting all reviewer comments blindly | May introduce inconsistencies or weaken valid arguments | Use External Review Protocol's strategic coaching |
| Running pipeline for a 1-page abstract | Overhead far exceeds benefit | Use academic-paper full directly |
| Using fact-check mode for literature review | Different purpose and methodology | Use deep-research full or systematic-review |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |