Professional domain 7 · Developer productivity and operational enablement

7% of the Professional exam · Last checked: 30 September 2026

• Configuring Claude Code for a team: commit the shared CLAUDE.md, .claude/settings.json and .mcp.json (with ${VAR} for secrets); keep personal settings in .claude/settings.local.json; use managed settings for organisation-wide policy. Other settings can't override them, apart from a few keys where a stricter local value still applies. Permission deny rules win over allow rules. Share skills and subagents through the repository or plugins.
• Better workflows: plan mode for large changes, -p (headless) in CI, GitHub Actions for pull-request work, subagents to keep the main context clean, /clear between unrelated tasks, checkpoints to undo Claude's edits.
• Operations: set CLAUDE_CODE_ENABLE_TELEMETRY=1 and choose exporters (OTEL_METRICS_EXPORTER for metrics, OTEL_LOGS_EXPORTER for events). Claude Code then exports OpenTelemetry data, including sessions, cost, tokens, lines changed, commits and pull requests. Administrators can enforce the setup through managed settings.
• Debugging: /doctor for installation and setup problems, /context to see what's loaded, --debug for detail, and settings precedence and permission rules when something is unexpectedly allowed or blocked.

See also: Foundations domain 3 · CLAUDE.md, rules and skills, Foundations domain 3 · Settings precedence, Foundations domain 2 · MCP servers in Claude Code, Foundations domain 1 · Subagents and coordination, Foundations domain 3 · Plan mode or direct execution?, Foundations domain 3 · Flags for headless and CI use and Foundations domain 3 · Commands, by symptom.

Docs: SettingsPermissionsMCP in Claude CodeMonitoring usageGitHub ActionsBest practices