Skip to content

Rule-doc drift: designate /manage-refs SKILL.md as canonical reference-workflow source #16

@Yoojin-nam

Description

@Yoojin-nam

Scope

The following user-scope rule files each describe partial reference workflows:

  • ~/.claude/rules/manuscript-references.md — Phase 1/2/3 hybrid, Skill discovery fallback list
  • ~/.claude/rules/zotero-workflow.md — Zotero MCP + BBT setup
  • ~/.claude/rules/agent-skill-routing.md — skill routing table for references
  • ~/.claude/rules/citation-safety.md — verify-refs strict-mode policy, v1.2.0 full-author requirement
  • ~/.claude/rules/senior-mentor-circulation.md — circulation folder structure, gate timing

After PR #13 lands (master pre-submission gate), these rules duplicate information that the repo skill docs already declare. Drift between user-rules and repo-skill-docs is the failure mode the discovery fallback (manuscript-references.md §Skill discovery 2026-05-13) currently papers over.

Proposed change

  • Designate skills/manage-refs/SKILL.md as the canonical source for reference-workflow orchestration
  • Designate skills/verify-refs/SKILL.md as the canonical source for bib audit
  • Each ~/.claude/rules/*.md file referencing references gets:
    • One-line pointer: "Canonical workflow: medsci-skills skills/manage-refs/SKILL.md (master gate)"
    • Existing prose pared down to user-scope rationale (why, when, project-level overrides) — not how
  • Skill SKILL.md files absorb the "how" details

Why this is a separate issue

User-scope rule files live outside the medsci-skills repo. The cleanup belongs to a different review surface (personal rules vs shared skills) and a different review timing (after the gate lands and proves stable).

Acceptance

  • After-PR-13 follow-up: each of the 5 rule files audited
  • Drift between user-rules and skill docs surfaced and resolved
  • Single canonical source designated in each rule file

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions