Skip to content

Product Main Repository AGENTS.md

Product-main repository AGENTS.md files tell Codex how to coordinate product work without drifting into implementation work.

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

flowchart TD
  agents["Product-main AGENTS.md"] --> productDocs["Product docs"]
  agents --> registry["Product repository registry"]
  agents --> issues["GitHub issues and project items"]
  issues --> implementation["Implementation repositories"]
  implementation --> reports["PR completion reports"]
  reports --> progress["Product-main progress docs"]

Required Emphasis

Product-main AGENTS.md should make these boundaries explicit:

  • the repository owns product coordination, not implementation code
  • implementation tasks should be handed off through GitHub issues and GitHub Project fields
  • product docs, repository registry, capability map, issues, PR completion reports, and project status should stay in sync
  • implementation details should live in the owning implementation repository
  • shared Anuva process changes belong in anuva-engineering-handbook

Read First

Point Codex to product-main source-of-truth docs, such as:

  • product bootstrap context
  • product vision, architecture, roadmap, and glossary
  • product repository registry
  • product capability map
  • product change workflow
  • GitHub Project workflow

Change Workflow

Product-main AGENTS.md should reference the local product-main workflow, usually:

docs/development/ProductChangeWorkflow.md

This workflow should route implementation work into repository-specific issues rather than local implementation edits.

Verification

Product-main verification is usually docs and coordination verification:

  • git diff --check
  • mkdocs build --strict
  • GitHub issue, PR, and Project field parity checks when applicable

Implementation tests run in the owning implementation repositories.