Product Main Repository AGENTS.md Template

Use this template for product-main repositories such as anuva-main-video-creator.

# AGENTS.md

This file applies to the `<product-main-repository>/` repository root.

## Repository Purpose

This repository owns product management and cross-repository coordination for `<product-name>`.

It is not an implementation repository and must not contain implementation code.

## Ownership Boundaries

This repository owns:

- product vision, roadmap, and architecture
- product repository registry
- product capability map
- cross-repository feature planning
- GitHub issue and GitHub Project coordination
- product-level prompts, templates, playbooks, releases, and ADRs

This repository does not own:

- implementation code
- repository-local implementation docs
- implementation tests or build output
- implementation repository `AGENTS.md` files unless the user explicitly opens that repository and asks Codex to work there

## Read First

- `docs/bootstrap/<Product>_Product.md`: product bootstrap context, if present.
- `docs/product/ProductVision.md`: product goals and durable product direction.
- `docs/product/ProductArchitecture.md`: product-level architecture.
- `docs/repositories/ProductRepositoryRegistry.md`: implementation repository ownership.
- `docs/capabilities/ProductCapabilityMap.md`: product capability ownership.
- `docs/development/ProductChangeWorkflow.md`: product-main change workflow.

## Common Commands

Run from the repository root.

- `git diff --check`
- `mkdocs build --strict`

## Working Rules

- Keep product-main work at product coordination level.
- Do not add implementation code.
- Create repository-specific GitHub issues for implementation work after product docs are reviewed.
- Treat GitHub issues as durable implementation handoff packets.
- Keep product docs, GitHub issues, PR completion reports, and GitHub Project fields in sync.
- Preserve unrelated user changes.

## Documentation Rules

- Update product docs when product behavior, repository ownership, capability ownership, or release readiness changes.
- Update product prompts and templates when coordination workflows change.
- Update `anuva-engineering-handbook` when shared Anuva process, templates, prompts, skills guidance, publishing structure, or registry rules change.
- Route aggregated publishing changes through `anuva-dev-docs` when configured.

## Change Workflow

Follow `docs/development/ProductChangeWorkflow.md` for product-main changes.

Use implementation repository issues for implementation work. Do not implement repository-local code from this repository unless the user explicitly switches to that repository.

## Verification

- Docs-only change: `git diff --check`
- Product docs build: `mkdocs build --strict`

If a check cannot be run, explain why in the final response.