Skip to content

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 | 完整论文流程, 从研究到论文, 端到端写论文, 论文流水线。

FileKindSize
SKILL.mdskill md58.4 KB
_shared/ARCHITECTURE.mdmarkdown51.7 KB
_shared/MODE_REGISTRY.mdmarkdown6.7 KB
_shared/agents/compliance_agent.mdmarkdown9.4 KB
_shared/artifact_reproducibility_pattern.mdmarkdown9.8 KB
_shared/benchmark_report.schema.jsonconfig2.7 KB
_shared/benchmark_report_pattern.mdmarkdown8.8 KB
_shared/bibliographic_integrity_signals.mdmarkdown8.1 KB
_shared/collaboration_depth_rubric.mdmarkdown11.5 KB
_shared/compliance_checkpoint_protocol.mdmarkdown8.9 KB
_shared/compliance_report.schema.jsonconfig8.1 KB
_shared/contracts/README.mdmarkdown54.7 KB
_shared/contracts/activity/adjudication_activity_input.schema.jsonconfig18.5 KB
_shared/contracts/activity/adjudication_activity_store.schema.jsonconfig18.7 KB
_shared/contracts/audit/audit_jsonl.schema.jsonconfig5.4 KB
_shared/contracts/audit/audit_sidecar.schema.jsonconfig8.4 KB
_shared/contracts/audit/audit_verdict.schema.jsonconfig5.4 KB
_shared/contracts/audit/cross_document_consistency_advisory.schema.jsonconfig20.4 KB
_shared/contracts/audit/cross_document_consistency_advisory_draft.schema.jsonconfig23.4 KB
_shared/contracts/audit/cross_document_source_manifest.schema.jsonconfig6.3 KB
_shared/contracts/audit/tortured_phrase_advisory.schema.jsonconfig30.9 KB
_shared/contracts/audit/tortured_phrase_snapshot.schema.jsonconfig4.9 KB
_shared/contracts/audit/tortured_phrase_snapshot_manifest.schema.jsonconfig7.3 KB
_shared/contracts/capability/stage_capability_matrix.jsonconfig23.5 KB
_shared/contracts/claim_standing/candidate_ledger.schema.jsonconfig23.1 KB
_shared/contracts/claim_standing/query_plan.schema.jsonconfig12.7 KB
_shared/contracts/claim_standing/query_plan_v1_1.schema.jsonconfig20.3 KB
_shared/contracts/claim_standing/retrieval_input.schema.jsonconfig14.4 KB
_shared/contracts/claim_standing/stance_record.schema.jsonconfig11.7 KB
_shared/contracts/claim_standing/transmission_ledger.schema.jsonconfig7.6 KB
_shared/contracts/cross_model/codex_citation_receipt.schema.jsonconfig4.7 KB
_shared/contracts/cross_model/codex_citation_request.schema.jsonconfig986 B
_shared/contracts/cross_model/promotion_bakeoff_sealed_commitment.schema.jsonconfig1.5 KB
_shared/contracts/cross_model/promotion_bakeoff_sealed_reveal.schema.jsonconfig1.5 KB
_shared/contracts/degradation_registry.jsonconfig42.5 KB
_shared/contracts/evaluator/full.jsonconfig6.3 KB
_shared/contracts/evidence/claim_registry.schema.jsonconfig2.3 KB
_shared/contracts/evidence/claim_registry_coverage_report.schema.jsonconfig4.8 KB
_shared/contracts/evidence/evidence_row.schema.jsonconfig14.3 KB
_shared/contracts/evidence/evidence_row_v1_1.schema.jsonconfig11.4 KB
_shared/contracts/evidence/evidence_row_v1_2.schema.jsonconfig21.8 KB
_shared/contracts/evidence/evidence_row_v1_3.schema.jsonconfig10.7 KB
_shared/contracts/human_subjects/authority_profile_registry.schema.jsonconfig16.7 KB
_shared/contracts/human_subjects/committee_correspondence.schema.jsonconfig9.9 KB
_shared/contracts/human_subjects/content_coverage_advisory.schema.jsonconfig19.9 KB
_shared/contracts/human_subjects/irb_context_record.schema.jsonconfig12.1 KB
_shared/contracts/human_subjects/resolved_authority_context.schema.jsonconfig11.8 KB
_shared/contracts/human_subjects/review_pathway_rule_trace.schema.jsonconfig9.5 KB
_shared/contracts/human_subjects/review_pathway_trace_request.schema.jsonconfig4.8 KB
_shared/contracts/human_subjects/submission_packet_inventory.schema.jsonconfig8.5 KB
_shared/contracts/human_subjects/submission_packet_manifest.schema.jsonconfig32.2 KB
_shared/contracts/passport/audit_artifact_entry.schema.jsonconfig10.8 KB
_shared/contracts/passport/bibliographic_integrity_signal.schema.jsonconfig48.9 KB
_shared/contracts/passport/citation_provenance.schema.jsonconfig4.8 KB
_shared/contracts/passport/citation_verification_summary.schema.jsonconfig8.2 KB
_shared/contracts/passport/claim_audit_result.schema.jsonconfig7.8 KB
_shared/contracts/passport/claim_drift.schema.jsonconfig3.8 KB
_shared/contracts/passport/claim_intent_manifest.schema.jsonconfig6.6 KB
_shared/contracts/passport/constraint_violation.schema.jsonconfig3.6 KB
_shared/contracts/passport/excluded_source_entry.schema.jsonconfig1.7 KB
_shared/contracts/passport/experiment_alignment_result.schema.jsonconfig4.8 KB
_shared/contracts/passport/experiment_provenance_entry.schema.jsonconfig10.0 KB
_shared/contracts/passport/human_read_log.schema.jsonconfig3.8 KB
_shared/contracts/passport/inquiry_ledger_ref.schema.jsonconfig881 B
_shared/contracts/passport/literature_corpus_entry.schema.jsonconfig30.3 KB
_shared/contracts/passport/preregistration_artifact.schema.jsonconfig4.3 KB
_shared/contracts/passport/rejection_log.schema.jsonconfig3.3 KB
_shared/contracts/passport/reset_ledger_entry.schema.jsonconfig7.1 KB
_shared/contracts/passport/run_ledger.schema.jsonconfig8.0 KB
_shared/contracts/passport/standing_constraint_entry.schema.jsonconfig2.6 KB
_shared/contracts/passport/temporal_audit_results.schema.jsonconfig8.8 KB
_shared/contracts/passport/terminal_policies.schema.jsonconfig8.1 KB
_shared/contracts/passport/timeline.schema.jsonconfig4.7 KB
_shared/contracts/passport/uncited_assertion.schema.jsonconfig3.3 KB
_shared/contracts/passport/uncited_audit_failure.schema.jsonconfig4.4 KB
_shared/contracts/passport/user_attested_read_resolution.schema.jsonconfig3.2 KB
_shared/contracts/passport/version_records.schema.jsonconfig4.9 KB
_shared/contracts/patch/block_manifest.schema.jsonconfig2.1 KB
_shared/contracts/patch/legacy/v1_0/revision_patch.schema.jsonconfig5.3 KB
_shared/contracts/patch/revision_patch.schema.jsonconfig8.9 KB
_shared/contracts/pdf/pdf_content_classifier_diagnostic.schema.jsonconfig1.2 KB
_shared/contracts/pdf/pdf_content_classifier_worker.schema.jsonconfig2.2 KB
_shared/contracts/pdf/pdf_read_preflight.schema.jsonconfig6.8 KB
_shared/contracts/re_review/input_manifest.schema.jsonconfig7.6 KB
_shared/contracts/re_review/legacy/v1_0/input_manifest.schema.jsonconfig6.2 KB
_shared/contracts/re_review/legacy/v1_0/precommitment.schema.jsonconfig8.9 KB
_shared/contracts/re_review/legacy/v1_0/traceability.schema.jsonconfig34.2 KB
_shared/contracts/re_review/legacy/v1_0/verdict_record.schema.jsonconfig10.5 KB
_shared/contracts/re_review/precommitment.schema.jsonconfig8.6 KB
_shared/contracts/re_review/traceability.schema.jsonconfig37.7 KB
_shared/contracts/re_review/verdict_record.schema.jsonconfig10.5 KB
_shared/contracts/research_workflow/inquiry_branch_ledger.schema.jsonconfig17.0 KB
_shared/contracts/research_workflow/research_workflow_profile.schema.jsonconfig7.2 KB
_shared/contracts/research_workflow/research_workflow_profile_selection_receipt.schema.jsonconfig3.9 KB
_shared/contracts/review_target/constructive_review_findings.schema.jsonconfig7.0 KB
_shared/contracts/review_target/criteria_registry.schema.jsonconfig4.0 KB
_shared/contracts/review_target/review_criteria_binding_manifest.schema.jsonconfig7.9 KB
_shared/contracts/review_target/review_criteria_source_receipt.schema.jsonconfig5.6 KB
_shared/contracts/review_target/review_target_context.schema.jsonconfig4.5 KB
_shared/contracts/review_target/review_target_declaration.schema.jsonconfig4.6 KB
_shared/contracts/reviewer/full.jsonconfig3.7 KB
_shared/contracts/reviewer/methodology_focus.jsonconfig2.2 KB
_shared/contracts/reviewer/review_panel_provenance.schema.jsonconfig7.8 KB
_shared/contracts/reviewer/review_panel_provenance_carrier.schema.jsonconfig4.1 KB
_shared/contracts/reviewer/review_panel_provenance_input.schema.jsonconfig3.5 KB
_shared/contracts/revision/author_adjudication.schema.jsonconfig7.8 KB
_shared/contracts/revision/author_adjudication_input.schema.jsonconfig1.2 KB
_shared/contracts/revision/claim_strength_drift_disposition.schema.jsonconfig3.6 KB
_shared/contracts/revision/claim_strength_drift_disposition_input.schema.jsonconfig3.1 KB
_shared/contracts/revision/claim_strength_drift_findings.schema.jsonconfig4.2 KB
_shared/contracts/revision/claim_surface_manifest.schema.jsonconfig3.3 KB
_shared/contracts/revision/integrity_correction_authorization.schema.jsonconfig4.3 KB
_shared/contracts/revision/integrity_correction_authorization_input.schema.jsonconfig1.5 KB
_shared/contracts/revision/integrity_correction_list.schema.jsonconfig1.8 KB
_shared/contracts/revision/integrity_pass_receipt.schema.jsonconfig809 B
_shared/contracts/revision/revision_evidence_bundle.schema.jsonconfig4.9 KB
_shared/contracts/revision/revision_roadmap.schema.jsonconfig11.2 KB
_shared/contracts/submission/format_profile.example.yamlconfig971 B
_shared/contracts/submission/format_profile.schema.jsonconfig4.6 KB
_shared/contracts/submission/submission_verification_report.schema.jsonconfig10.3 KB
_shared/contracts/submission/venue_profile.schema.jsonconfig4.1 KB
_shared/contracts/writer/full.jsonconfig3.6 KB
_shared/cross_model_verification.mdmarkdown83.3 KB
_shared/description-original.mdmarkdown904 B
_shared/dsh-runtime.mdmarkdown1.5 KB
_shared/evals_lift_report.schema.jsonconfig5.0 KB
_shared/ground_truth_isolation_pattern.mdmarkdown16.0 KB
_shared/handoff_schemas.mdmarkdown96.9 KB
_shared/human_subjects_authority_registry.jsonconfig49.5 KB
_shared/mode_spectrum.mdmarkdown5.2 KB
_shared/model_tiering.mdmarkdown12.6 KB
_shared/output_language_pair.mdmarkdown7.7 KB
_shared/policy_data/nature_policy.mdmarkdown3.9 KB
_shared/prisma_trAIce_protocol.mdmarkdown10.2 KB
_shared/raise_framework.mdmarkdown7.5 KB
_shared/references/authority_content_coverage_advisory_protocol.mdmarkdown14.0 KB
_shared/references/claim_standing_candidate_ledger_protocol.mdmarkdown19.2 KB
_shared/references/claim_strength_ladder.mdmarkdown5.5 KB
_shared/references/cross_document_consistency_advisory_protocol.mdmarkdown13.5 KB
_shared/references/evidence_row_protocol.mdmarkdown14.4 KB
_shared/references/firm_rules.mdmarkdown11.0 KB
_shared/references/human_subjects_authority_protocol.mdmarkdown13.1 KB
_shared/references/intent_clarification_protocol.mdmarkdown11.9 KB
_shared/references/irb_terminology_glossary.mdmarkdown12.4 KB
_shared/references/per_source_method_weaknesses.mdmarkdown4.2 KB
_shared/references/protected_hedging_phrases.mdmarkdown8.9 KB
_shared/references/psychometric_terminology_glossary.mdmarkdown8.7 KB
_shared/references/review_criteria_consumer_protocol.mdmarkdown10.3 KB
_shared/references/review_form_note.mdmarkdown11.3 KB
_shared/references/review_pathway_rule_trace_protocol.mdmarkdown8.3 KB
_shared/references/routing_core.mdmarkdown5.7 KB
_shared/references/submission_packet_manifest_protocol.mdmarkdown13.6 KB
_shared/references/word_count_conventions.mdmarkdown9.0 KB
_shared/research_workflow_profiles/field_general.jsonconfig1.2 KB
_shared/review_criteria_registry.jsonconfig11.5 KB
_shared/review_criteria_sources/msr-2027-technical-papers.2026-08-24.jsonconfig2.0 KB
_shared/review_criteria_sources/sigsoft-empirical-standards.2026-08-24.jsonconfig1.4 KB
_shared/sprint_contract.schema.jsonconfig19.0 KB
_shared/style_calibration_protocol.mdmarkdown6.9 KB
_shared/templates/codex_audit_multifile_template.mdmarkdown16.7 KB
agents/claim_ref_alignment_audit_agent.mdmarkdown45.0 KB
agents/collaboration_depth_agent.mdmarkdown10.4 KB
agents/integrity_verification_agent.mdmarkdown75.2 KB
agents/pipeline_orchestrator_agent.mdmarkdown175.5 KB
agents/state_tracker_agent.mdmarkdown27.4 KB
examples/full_pipeline_example.mdmarkdown17.7 KB
examples/integrity_failure_recovery.mdmarkdown26.8 KB
examples/mid_entry_example.mdmarkdown13.4 KB
references/adapters/.gitkeepother0 B
references/adapters/overview.mdmarkdown10.0 KB
references/ai_research_failure_modes.mdmarkdown16.3 KB
references/changelog.mdmarkdown6.4 KB
references/claim_audit_calibration_protocol.mdmarkdown14.9 KB
references/claim_verification_protocol.mdmarkdown31.1 KB
references/external_review_protocol.mdmarkdown6.8 KB
references/integrity_review_protocol.mdmarkdown7.8 KB
references/literature_corpus_consumers.mdmarkdown12.3 KB
references/mode_advisor.mdmarkdown8.7 KB
references/passport_as_reset_boundary.mdmarkdown19.3 KB
references/pipeline_state_machine.mdmarkdown29.0 KB
references/plagiarism_detection_protocol.mdmarkdown14.1 KB
references/process_summary_protocol.mdmarkdown16.4 KB
references/progress_dashboard_template.mdmarkdown2.1 KB
references/reinforcement_content.mdmarkdown2.0 KB
references/reproducibility_audit.mdmarkdown3.2 KB
references/score_trajectory_protocol.mdmarkdown4.5 KB
references/team_collaboration_protocol.mdmarkdown10.7 KB
references/two_stage_review_protocol.mdmarkdown3.6 KB
scripts/_claim_audit_constants.pyscript13.7 KB
scripts/_markdown_lint_util.pyscript9.0 KB
scripts/_next_verified_at_ms.pyscript6.5 KB
scripts/_skill_lint.pyscript13.6 KB
scripts/ars_anchorize_draft.pyscript5.8 KB
scripts/ars_apply_revision_patch.pyscript36.2 KB
scripts/ars_cache_invalidate.pyscript1.3 KB
scripts/ars_mark_read.pyscript18.2 KB
scripts/ars_write_scope_guard.pyscript30.9 KB
scripts/audit_snapshot.pyscript23.5 KB
scripts/bibliographic_integrity_signals.pyscript32.2 KB
scripts/build_claim_standing_candidate_ledger.pyscript54.3 KB

references/team_collaboration_protocol.md

View on GitHub
> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Team Collaboration Protocol

## Purpose

Guidelines for coordinating multi-person academic research teams using the pipeline. Claude Code runs as a single-user session; this protocol documents the **human coordination layer** that wraps around pipeline executions.

---

## Role Definitions

| Role | Pipeline Stages | Responsibilities |
|------|----------------|-----------------|
| Research Lead | Stage 1 (RESEARCH) | Defines RQ, manages literature search, approves synthesis, sets theoretical framework |
| Lead Author | Stage 2 (WRITE), Stage 4/4' (REVISE) | Writes/revises paper, makes final content decisions, owns the manuscript |
| Methods Specialist | Stage 1 (methodology), Stage 2 (methods section) | Ensures methodological rigor, validates statistical analysis, reviews data integrity |
| Review Coordinator | Stage 3/3' (REVIEW) | Manages simulated review process, distributes feedback, facilitates revision coaching |
| Integration Lead | All stages | Ensures consistency across stages, manages handoffs, resolves cross-stage conflicts |

### Role Assignment Rules

- One person may hold multiple roles (common in small teams)
- Research Lead and Lead Author are the minimum required roles (can be the same person)
- Integration Lead is recommended for teams of 3+
- Methods Specialist is strongly recommended for empirical papers
- All role assignments should be documented at pipeline intake

---

## Handoff Protocol

For each stage transition, the following handoff procedure applies:

### Stage 1 -> Stage 2 (Research -> Write)

| Item | Detail |
|------|--------|
| **Who hands off** | Research Lead |
| **Who receives** | Lead Author |
| **Materials** | RQ Brief, Bibliography, Synthesis Report (conforming to Schemas 1-3 in `_shared/handoff_schemas.md`) |
| **Approval needed** | Research Lead confirms synthesis is complete and RQ is finalized |
| **Handoff checklist** | All Material Passports (Schema 9) attached; bibliography coverage is assessed against the planned claims and field-specific evidence needs; synthesis structure fits the material rather than a fixed theme count |

### Stage 2 -> Stage 2.5 (Write -> Integrity)

| Item | Detail |
|------|--------|
| **Who hands off** | Lead Author |
| **Who receives** | Integration Lead (or Lead Author if no Integration Lead) |
| **Materials** | Paper Draft (conforming to Schema 4) |
| **Approval needed** | Lead Author confirms draft is ready for verification |
| **Handoff checklist** | All sections complete; reference list formatted; word count within target range |

### Stage 2.5 -> Stage 3 (Integrity -> Review)

| Item | Detail |
|------|--------|
| **Who hands off** | Integration Lead |
| **Who receives** | Review Coordinator |
| **Materials** | Stage 2.5 Paper Draft (verified, or carrying the recorded FAIL-loop warning) + Integrity Report (Schema 5) |
| **Approval needed** | Integrity verdict is PASS (any PASS_WITH_CONDITIONS items acknowledged), or the recorded Integrity Check FAIL Loop user decision |
| **Handoff checklist** | Integrity Report attached; all SERIOUS/MEDIUM issues resolved, or covered by the recorded FAIL-loop decision |

### Stage 3 -> Stage 4 (Review -> Revise)

| Item | Detail |
|------|--------|
| **Who hands off** | Review Coordinator |
| **Who receives** | Lead Author + Methods Specialist (if methodology issues) |
| **Materials** | Review Report (Schema 6) + Revision Roadmap (Schema 7) |
| **Approval needed** | Review Coordinator confirms roadmap is complete; Lead Author reviews before starting |
| **Handoff checklist** | All revision items categorized and prioritized; coaching session completed (or skipped by Lead Author) |

### Stage 4 -> Stage 3' (Revise -> Re-Review)

| Item | Detail |
|------|--------|
| **Who hands off** | Lead Author |
| **Who receives** | Review Coordinator |
| **Materials** | Revised Draft + hard-required Original pre-revision Draft + immutable Round-1 Revision Roadmap + exact author-adjudication sidecar + fully replayed Revision-Evidence Bundle + Response to Reviewers + Editorial Decision Letter + Round-1 findings + exact ordered patch/report pairs matching the bundle + Round-1 Reviewer Configuration Cards. This is the default current #576 1.1 re-review transfer; missing original/roadmap/author/bundle fails closed. A user-requested fresh full review at 3' is a separate branch with Revised Draft + available context. |
| **Approval needed** | Lead Author confirms all addressable items are handled |
| **Handoff checklist** | Re-review mode: Response to Reviewers covers every roadmap item; new references verified. Fresh full review at 3': no roadmap-coverage check (no Round-1 Roadmap exists); new references verified |

### Stage 4.5 -> Stage 5 (Final Integrity -> Finalize)

| Item | Detail |
|------|--------|
| **Who hands off** | Integration Lead |
| **Who receives** | Lead Author |
| **Materials** | Final Draft (verified, or carrying the recorded partially-unverified warning) + Final Integrity Report |
| **Approval needed** | Integrity verdict PASS with zero issues (or the recorded Integrity Check FAIL Loop user decision) |
| **Handoff checklist** | All previous integrity issues resolved, or covered by the recorded FAIL-loop decision with the partially-unverified warning carried forward; Material Passport `verification_status` set to `VERIFIED` only on a zero-issue PASS (a FAIL-loop continuation keeps `UNVERIFIED`) |

---

## Version Control

### Git Branching Strategy

```
main
  |-- paper/draft-v1          (Stage 2 output)
  |-- paper/post-integrity-v1 (Stage 2.5 output)
  |-- paper/post-review-v1    (Stage 4 output)
  |-- paper/final-v1          (Stage 5 output)
```

### Tagging Convention

| Tag | When | Example |
|-----|------|---------|
| `v0.1-draft` | After Stage 2 completion | First complete draft |
| `v0.2-post-integrity` | After Stage 2.5 PASS | Draft verified for integrity |
| `v0.3-post-review` | After Stage 4 completion | First revision complete |
| `v0.4-post-rereview` | After Stage 4' completion (if applicable) | Second revision complete |
| `v1.0-final` | After Stage 5 completion | Final manuscript |

### Rules

- Never overwrite; always create a new version
- All versions are preserved for audit trail
- Version labels must match the Material Passport `version_label` field (Schema 9 in `_shared/handoff_schemas.md`)
- Each team member's changes should be attributable (use git author info)

---

## Conflict Resolution

| Conflict Type | Resolution Authority | Escalation Path |
|--------------|---------------------|-----------------|
| Content disagreements | Lead Author has final say | If unresolved: Research Lead mediates |
| Methodological disagreements | Methods Specialist has final say | If unresolved: cite literature precedent |
| Scope disagreements | Research Lead has final say | If unresolved: team vote |
| Formatting/style disagreements | Lead Author has final say | Follow target journal guidelines |
| Integrity findings disagreements | Integration Lead has final say | Cannot override SERIOUS findings |

### Disagreement Documentation

All disagreements must be documented in the revision tracking:

```markdown
## Disagreement Record

**Date**: [date]
**Stage**: [stage]
**Parties**: [who disagreed]
**Issue**: [what the disagreement was about]
**Resolution**: [how it was resolved]
**Authority**: [who made the final call]
**Rationale**: [why this decision was made]
```

---

## Communication Templates

### 1. Handoff Notification

```markdown
## Handoff: Stage [X] -> Stage [Y]

**From**: [Role] ([Name])
**To**: [Role] ([Name])
**Date**: [date]

**Materials Delivered**:
- [Material 1] (version: [version_label])
- [Material 2] (version: [version_label])

**Status Summary**:
[1-2 sentence summary of what was accomplished and any open items]

**Action Required**:
[What the receiving person needs to do next]

**Deadline**: [if applicable]
```

### 2. Review Request

```markdown
## Review Request: [Paper Title]

**From**: [Review Coordinator]
**To**: [Team / External Reviewer]
**Date**: [date]

**Paper Version**: [version_label]
**Word Count**: [N]
**Review Type**: [Internal simulated / External journal / Team peer review]

**Focus Areas**:
1. [specific area to focus on]
2. [specific area to focus on]

**Deadline**: [date]
**Return Format**: [Use Schema 6 format from _shared/handoff_schemas.md]
```

### 3. Revision Assignment

```markdown
## Revision Assignment: [Paper Title]

**From**: [Review Coordinator]
**To**: [Lead Author / Methods Specialist]
**Date**: [date]

**Revision Round**: [N]
**Total Items**: [N] (must_fix: [N], should_fix: [N], consider: [N])

**Your Assignments**:
- [REV-001]: [brief description] — assigned to [name]
- [REV-003]: [brief description] — assigned to [name]

**Deadline**: [date]
**Coordination Notes**: [any dependencies between revision items]
```

---

## Workflow for Teams

### Small Team (2-3 people)

```
Person A (Research Lead + Lead Author):
  - Runs Stage 1 (RESEARCH) with their Claude session
  - Runs Stage 2 (WRITE) with their Claude session
  - Receives revision items, runs Stage 4/4'
  - Runs Stage 5 (FINALIZE)

Person B (Methods Specialist + Review Coordinator):
  - Reviews Stage 1 methodology output
  - Reviews Stage 2 methods section
  - Manages Stage 3/3' review process
  - Handles specific methodology revision items

Handoff: via shared folder or git repo
Materials: conform to schemas in _shared/handoff_schemas.md
```

### Large Team (4+ people)

```
Add Integration Lead role:
  - Monitors all stage transitions
  - Validates handoff completeness
  - Resolves cross-stage inconsistencies
  - Maintains pipeline state document (shared with all team members)
```

---

## Limitations

- Claude Code runs as a single-user session; this protocol documents the HUMAN coordination layer
- Each team member runs their own pipeline stages independently in separate Claude sessions
- Handoff materials (conforming to schemas in `_shared/handoff_schemas.md`) ensure consistency across sessions
- Real-time co-editing is not supported; use git or shared documents for synchronization
- Pipeline state tracking is per-session; the Integration Lead must manually synchronize state across sessions
- The pipeline does not enforce team role permissions; discipline is maintained by convention
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall