# Clinic Agent Guidance and Module Overview Plan

## Goal

- Require a dated implementation plan for every Clinic source, configuration, or documentation change.
- Clarify the commit and pull request handoff, including explicit user confirmation and English PR content.
- Add a maintained repository module overview that maps source ownership to build outputs and app-delivery deployment paths.
- Keep local setup instructions portable across developers' workstation directory layouts.

## Scope

- Update the root `AGENTS.md` development workflow.
- Add `docs/clinic-module-overview.md` as the standalone module and deployment map.
- Document the current root Go module, nested Go modules, operational tools, GitHub Actions workflows, and Clinic-related app-delivery directories.
- Keep the existing system-log, staging validation, review, and production authorization boundaries unchanged.

## Implementation

1. Scan the Clinic repository structure, Go module boundaries, command entrypoints, Docker build targets, and GitHub Actions workflows.
2. Scan the corresponding app-delivery staging and production Kustomize directories and the Clinic version-bump workflow.
3. Create a module overview that distinguishes source packages, executable components, container images, and deployment ownership.
4. Add plan requirements and naming rules to `AGENTS.md`.
5. Require the agent to ask whether to commit, push, and create a PR after validation unless the user already authorized those actions.
6. Require English PR titles and descriptions that explain the goal, implementation, scope, validation, and deployment impact.
7. Link the standalone module overview from `AGENTS.md` and require it to be updated when module or deployment ownership changes.
8. Resolve the `nutshell-skills` checkout relative to the Clinic repository by default, retain environment-variable overrides, and avoid user-specific absolute paths.

## Validation

- Confirm the documented Go modules and command entrypoints exist in the current branch.
- Confirm the documented app-delivery paths and image mappings exist in the current app-delivery checkout.
- Run `git diff --check`.
- Confirm the tracked diff contains only the intended documentation files.
- Review Markdown headings, tables, links, and code fences.
- Confirm the changed documentation contains no user-specific home directory or IDE workspace path.

## Non-Goals

- Do not change application code, APIs, timeouts, Kubernetes manifests, GitHub Actions, or deployed environments.
- Do not update app-delivery in this change.
- Do not merge or release either repository.