Cursor Doctor

When the user invokes doctor or cursor doctor (or asks to audit the project for documentation, rules, and skills):

1. Use the MCP server in planning mode

• Call the cursor-doctor-self MCP server.
• Invoke generate_prescription so the project is audited and cursor-doctor-prescription-plan.md is written to the project root with YAML frontmatter todos.

2. Treat the prescription as the plan

• The plan file has frontmatter-style todos in the todos array (id, tier, status, concept, priority, and optional prompt, found_at, details).
• Run in planning mode: create or sync your task list from these frontmatter todos. Each todo with status missing or incomplete has a prompt directing what to create or update.
• The final todo is always Update Artifacts (artifact-sync): after working through the plan, review and update rules, skills, and docs affected by the session.

3. Work through the plan

• Process todos in order (by tier and list order). Use each todo’s prompt when creating or updating artifacts.
• When done with implementation work, complete the Update Artifacts step so rules, skills, and docs stay in sync.

Optional: audit only

If the user only wants an audit without writing the plan file, use audit_project from cursor-doctor-self and summarize gaps. For a full prescription with frontmatter todos, use generate_prescription.