Skip to content

zrwangems/dsh-zrwang-plugin / ars/skills/academic-pipeline

academic-pipeline

Unverified

学术研究总编排:研究→写作→诚信检查→评审→返修→复审→终检→定稿的十阶段流水线,每阶段停在用户确认点,含材料护照与 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/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
scripts/build_claim_standing_query_plan.pyscript25.0 KB

_shared/references/review_criteria_consumer_protocol.md

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

This protocol binds the #683 `ReviewTargetContext` across formative planning,
the academic-paper internal evaluator, and the academic-paper-reviewer external
panel. The binding is workflow conformance only. It never determines severity,
an editorial verdict, a checkpoint state, or author triage.

Normative design:
`docs/design/2026-08-11-684-review-criteria-consumer-binding-spec.md`.
Schemas:
`_shared/contracts/review_target/review_criteria_binding_manifest.schema.json`
and
`_shared/contracts/review_target/constructive_review_findings.schema.json`.
Tool: `scripts/review_criteria_binding.py`.

## 1. Inputs and authority

The orchestrating layer receives four explicit inputs:

1. the author-confirmed `ReviewTargetDeclaration` already embedded in the
   resolved context;
2. the exact `ReviewTargetContext` JSON;
3. the exact criteria registry named by that context; and
4. a caller-supplied `target_review_id`.

Initialize one manifest before any of the three consumers run:

```bash
python scripts/review_criteria_binding.py init \
  --context phase0/review_target_context.json \
  --context-ref phase0/review_target_context.json \
  --registry _shared/review_criteria_registry.json \
  --registry-ref _shared/review_criteria_registry.json \
  --target-review-id review-001 \
  --output phase0/review_criteria_binding.json
```

If an active manifest exists, pass it as `--prior-manifest`. A substantive
context change under the same `target_review_id` is a conflict. Starting a new
target review requires a new id and makes the predecessor non-comparable.

The manifest is the exact source of:

- `context_ref` and its raw SHA-256;
- `resolved_digest`;
- ordered `selected_criterion_ids`;
- exact criterion id/version/content-digest pointers;
- unresolved target dimensions; and
- parallel interdisciplinary conflict groups.

Consumers never reconstruct these fields from the Markdown brief and never
copy registry statements into their own instruction files.

## 2. Marker and receipt lifecycle

Before dispatch, render the role-specific marker:

```bash
python scripts/review_criteria_binding.py marker \
  --manifest phase0/review_criteria_binding.json \
  --consumer formative_planning --role FORMATIVE
```

The marker is appended verbatim to the consumer's output. After a successful
consumer call, the output also carries exactly one
`criteria_parallel_conflicts: <canonical compact JSON array>` line rendered
from the manifest. Record only explicitly named artifacts:

```bash
python scripts/review_criteria_binding.py record \
  --manifest phase0/review_criteria_binding.json \
  --consumer formative_planning \
  --artifact FORMATIVE=phase2/paper_outline.md
```

The internal receipt similarly names the paper-blind Phase 6a artifact, not
the later paper-visible decision:

```bash
python scripts/review_criteria_binding.py record \
  --manifest phase0/review_criteria_binding.json \
  --consumer internal_evaluator \
  --artifact INTERNAL=phase6/phase6a_precommitment.md
```

For the external panel, supply all five Phase 1 artifacts in one call:

```bash
python scripts/review_criteria_binding.py record \
  --manifest phase0/review_criteria_binding.json \
  --consumer external_panel \
  --artifact EIC=phase1/eic.md --artifact R1=phase1/methodology.md \
  --artifact R2=phase1/domain.md --artifact R3=phase1/perspective.md \
  --artifact DA=phase1/da.md
```

The recorder checks the complete marker and exact conflict line inside every
artifact, computes raw hashes itself, and appends one receipt atomically. Exact
retry is a no-write. Same-consumer drift is a conflict.

Before a review crosses its handoff boundary, run:

```bash
python scripts/review_criteria_binding.py validate \
  --manifest phase0/review_criteria_binding.json \
  --context phase0/review_target_context.json \
  --registry _shared/review_criteria_registry.json \
  --require-complete
```

## 3. Formative planning and writing

Owner: `academic-paper` Phase 2 `structure_architect_agent`.

- Phase 0 resolves the author-confirmed target before Phase 2.
- The Structure Architect receives the pointer-only context and Target Criteria
  Brief. Its outline names relevant criterion ids beside planned sections and
  evidence needs, while keeping scientific validity, venue fit, and submission
  readiness separate.
- `argument_builder_agent` and `draft_writer_agent` consume the same context
  pointer and the Structure Architect's receipt. They do not create a second
  receipt, re-resolve the target, copy criterion prose into their prompts, or
  silently change the author's contribution claim.
- A criterion can motivate a planned check; it never licenses invented evidence,
  results, methods, or a new research question.

The formative output records `FORMATIVE` with the exact marker.

## 4. Internal evaluator

Owner: `academic-paper` Phase 6 `peer_reviewer_agent`.

- Phase 6a receives the sprint/evaluator contract, paper metadata, the
  pointer-only context, and Target Criteria Brief. It remains paper-blind.
- Phase 6a commits the selected criterion ids and keeps each
  `parallel_conflicts[]` group separate. It does not declare applicability.
- The Phase 6a artifact records the `INTERNAL` receipt before any draft is
  visible. Phase 6b receives that unchanged artifact and the draft, assesses
  applicability, repeats the continuity marker, and emits its Critical/Major
  constructive sidecar when applicable.

The internal evaluator may identify a scientific-validity problem independent
of venue fit. It may not turn missing or advisory venue guidance into a blocking
finding.

## 5. External panel, including DA

Owner: the academic-paper-reviewer orchestrating layer.

- Phase 0 uses author-confirmed target metadata. `field_analyst_agent` may
  suggest panel expertise but cannot infer or overwrite venue/track/type.
- Each of `EIC`, `R1`, `R2`, `R3`, and `DA` receives the same context authority
  and brief during the existing paper-content-blind Phase 1 call.
- Each Phase 1 output repeats its role-specific marker and commits the selected
  criterion ids. Conflicting criteria stay parallel.
- Phase 2 receives the unchanged Phase 1 output plus manuscript data. Findings
  cite exact criterion pointers and manuscript evidence/absence anchors.
- `editorial_synthesizer_agent` checks all five marker bindings before
  synthesis. Missing or mismatched bindings abort the criteria-aware run; the
  synthesizer never silently falls back to a self-recalled target.

DA adversarial register does not relax the finding contract. Every DA Critical
or Major item enters the same constructive sidecar and carries the same remedy,
cost, trade-off, author-intent, and no-honest-remedy fields as another seat.

## 6. Constructive finding sidecar

The sidecar covers Critical/Major weaknesses only. Minor and copyedit channels
retain their existing formats. Validate it with:

```bash
python scripts/review_criteria_binding.py validate-findings \
  --manifest phase0/review_criteria_binding.json \
  --context phase0/review_target_context.json \
  --registry _shared/review_criteria_registry.json \
  --findings phase2/constructive_review_findings.json
```

Every row separates:

- criterion pointers from manuscript evidence;
- scholarly relevance from confirmed-target relevance;
- the minimum viable remedy from a stronger costlier option;
- effort scope from trade-offs; and
- reviewer advice from author-owned research intent.

If no honest remedy exists, `remedy_status=none`, both option fields are null,
and `no_honest_remedy_reason` explains why. If a stronger option is not
meaningful, it is null and `stronger_option_reason` explains why. An available
option always records `proposed_result_values=false`; new data or intent change
is an author choice, not an assertion that work or results exist.

A stale/unverified or otherwise non-blocking criterion may appear in ordinary
advisory prose, but the validator rejects a Critical/Major sidecar row whose
every criterion pointer has `blocking_eligible=false`.

## 7. Interdisciplinary applicability

Phase 1 commits each selected pointer without manuscript-derived applicability.
After the paper-visible boundary, a consumer may state:

- `applicable`, with a manuscript evidence/absence anchor;
- `not_applicable`, with a manuscript-grounded rationale; or
- `unresolved`, requiring human resolution.

No consumer averages parallel criteria, assigns an adaptive numeric weight, or
selects the criterion whose outcome is easiest to satisfy. Human resolution
belongs in a separate author/reviewer record and starts a new target review if
it changes the selected context.

## 8. Failures and degradation

Binding failures are visible workflow-conformance failures:

- malformed/oversized/symlinked input;
- context or registry hash drift;
- context recomputation mismatch;
- missing/duplicate/wrong-role receipt;
- missing or altered marker;
- selected-pointer mismatch;
- same-id profile change; or
- invalid constructive sidecar.

They stop only the criteria-aware handoff. They do not create an editorial
decision. The user may correct the artifacts, explicitly start a new target
review, or run the pre-#684 field-general workflow with an explicit
`criteria_binding_unavailable` disclosure. That degraded path makes no venue-
alignment claim and is non-comparable to a bound treatment run.

## 9. Measurement boundary

`evals/heldout/review_criteria_constructive_value/measurement_plan.md` owns the
paired behavioral design. CI validates schemas, fixtures, scorer behavior, and
prompt wiring only. It never dispatches a model, judge, or network request.

Until a valid `heldout-measurement/1.1` report is published, describe the
mechanism as implemented but its effect on unsupported-finding rate, severity,
venue alignment, and usefulness as **unmeasured**.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated 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