decide whether to rename Me Doctor

[pirog]

Context

The repository's read-only diagnostic skill is currently exposed as Me Doctor through $piro-me-doctor. Earlier repository naming used “me” broadly, while newer skills and terminology have become more domain-oriented. The current name now feels potentially inconsistent and is worth revisiting before more documentation and integrations depend on it.

Outcome

An evidence-backed decision determines whether Me Doctor remains the right public name, and the repository's owned naming surfaces are left coherent with that decision.

Scope

• Inventory the current Me Doctor, piro-me-doctor, and me-doctor public and internal naming surfaces
• Compare the name with the repository's current skill-naming conventions and the diagnostic skill's actual responsibility
• Decide whether to retain or rename the skill, including compatibility and migration implications
• Implement the selected bounded naming outcome consistently across owned source, documentation, tests, and managed cache inputs when a change is warranted

Out of scope

• A broad rename or cleanup of unrelated skills
• Behavioral changes to the diagnostic checks beyond what is necessary to preserve naming compatibility

Acceptance criteria

• The linked completion pull request records a clear retain-or-rename decision and its evidence-based rationale
• Every owned Me Doctor, piro-me-doctor, and me-doctor reference is inventoried and classified as retained or changed
• If renamed, public invocation, display metadata, documentation, tests, links, and managed cache source remain consistent and the compatibility or migration path is explicit
• If retained, an appropriate checked-in repository surface records why the name still fits the skill and current naming conventions
• Relevant focused validation and the repository's Codex cache convergence checks pass

Delivery and verification

Use one linked completion pull request, kept in draft while the decision and any bounded rename are developed. The pull request must include the reference inventory, decision rationale, applicable checked-in naming changes or retained-name rationale, focused skill validation, relevant tests and lint, and the codex:check / codex:sync / codex:check result.

Constraints and approvals

Task creation does not presume that a rename is desirable. Preserve existing $piro-me-doctor compatibility unless the reviewed decision explicitly justifies and documents a migration.

Task metadata

schema: tanaab/task-metadata/v2
mode: fallback
fallback:
  type: task
  priority: low
  work-size: 3
  complexity: medium
  impact: low