Summary

Add a parsec doctor --ai subcommand that prints parsec workflow rules to stdout in a structured format that any AI coding agent can consume.

Motivation

AI coding agents (Claude Code, Cursor, Copilot, Windsurf, etc.) often mix raw git/gh commands instead of using parsec's workflow. A tool-agnostic way to communicate "how to use parsec" is needed — not tied to any specific AI's config format (e.g., CLAUDE.md).

Proposed Behavior

$ parsec doctor --ai

Outputs a markdown document to stdout containing:

• Available parsec commands and when to use them
• Workflow rules (e.g., "always use parsec start instead of git worktree add")
• Current project config (layout, tracker provider, branch prefix)
• Common patterns: parsec start TICKET → parsec ship TICKET → parsec ci TICKET → parsec merge TICKET

Usage by AI agents

Any AI agent can run this command and include the output in its context:

• Claude Code: hook or CLAUDE.md can reference $(parsec doctor --ai)
• Cursor: .cursorrules can include the output
• Copilot/Windsurf: respective config files
• Generic: pipe to any LLM context window

Acceptance Criteria

• parsec doctor --ai outputs structured markdown to stdout
• Output includes current project config (layout, tracker, branch prefix)
• Output includes workflow rules and command reference
• Supports --json for machine-readable format
• No interactive prompts (safe for scripts/AI)