Skip to content

Anuva Engineering Handbook

Bootstrap Product Main Repository

Prompt: Bootstrap Product Main Repository

Use this prompt inside a new or existing product-main repository. Replace bracketed placeholders before running it.

Bootstrap this repository as the Product / Program Management repository for [Product Name].

Repository purpose:
This repository is not an implementation repository. It coordinates [Product Name] across its product implementation repositories.

Shared Engineering Platform:
- anuva-engineering-handbook defines engineering-wide process, AGENTS.md guidance, product-main and implementation repository change workflow patterns, templates, prompts, skills guidance, repository architecture, and capability ownership rules.
- anuva-dev-docs publishes aggregated development docs from Anuva repositories when MkDocs output is available.

Product implementation repositories:
- [implementation-repository-1]
- [implementation-repository-2]
- [implementation-repository-3]

First inspect the repository structure, existing docs, existing AGENTS.md, mkdocs.yml, package/build files, and any bootstrap context documents. Preserve useful existing content.

Create or update these top-level files:
- README.md
- AGENTS.md
- mkdocs.yml

Create or update this docs structure:
- docs/index.md
- docs/bootstrap/[Product]_Product.md, if a bootstrap context document exists or is provided
- docs/product/ProductVision.md
- docs/product/ProductArchitecture.md
- docs/product/ProductRoadmap.md
- docs/product/ProductGlossary.md
- docs/repositories/ProductRepositoryRegistry.md
- docs/capabilities/ProductCapabilityMap.md
- docs/development/ProductChangeWorkflow.md
- docs/development/CrossRepositoryFeatureWorkflow.md
- docs/development/DocsParityRules.md
- docs/development/GitHubProjectWorkflow.md
- docs/skills/ProductSkillsOverview.md
- docs/playbooks/index.md
- docs/prompts/index.md
- docs/prompts/GenerateImplementationBootstrapContext.md
- docs/prompts/PlanCrossRepositoryFeature.md
- docs/prompts/CreateGitHubProjectTasks.md
- docs/prompts/CreateRepositoryTask.md
- docs/prompts/ImplementGitHubProjectIssue.md
- docs/prompts/ReviewFeatureCompletion.md
- docs/templates/ProductFeature_Template.md
- docs/templates/RepositoryImpact_Template.md
- docs/templates/ProductADR_Template.md
- docs/adr/index.md
- docs/releases/index.md
- docs/changes/index.md

AGENTS.md requirements:
- State that this repo owns [Product Name] product coordination, not implementation.
- State that it may create product-level plans, repository impact analyses, product ADRs, release notes, product playbooks, product-specific prompts, GitHub issues, and GitHub Project items.
- State that it must not directly modify implementation repositories unless the user explicitly opens those repositories and asks Codex to work there.
- State that it follows the engineering process defined by anuva-engineering-handbook.
- State that it should produce repository-specific GitHub issues as durable implementation handoffs after product docs are reviewed.
- State that product docs, product repository registry, product capability map, GitHub issues, PR completion reports, and GitHub Project fields must stay in sync.
- State that docs publishing impact should be routed through anuva-dev-docs.

MkDocs requirements:
- Use Material for MkDocs.
- Add navigation for Product, Repositories, Capabilities, Development, Skills, Playbooks, Prompts, Templates, ADRs, Releases, and Changes.
- Use Mermaid-compatible fenced code blocks.
- Include at least one Mermaid diagram in each major architecture or process page.

Initial content requirements:
- Define [Product Name] as a product under the Shoonya Organization.
- Define the role of anuva-engineering-handbook as the shared Engineering Platform.
- Define the product repository hierarchy:
  [product-main-repository] -> [implementation-repository-1], [implementation-repository-2], [implementation-repository-3]
- Keep content product-level and avoid low-level implementation details.
- Add reusable prompts for asking Codex to create GitHub issues, update GitHub Project fields, and implement selected repository issues.
- Add a reusable prompt for generating implementation repository BootstrapContext.md content that can be copied into docs/bootstrap/BootstrapContext.md in the target implementation repository.
- Add placeholder playbook content only where it clarifies the product coordination model.
- Add an example feature change folder structure containing FeatureBrief.md, RepositoryImpact.md, HandoffPrompts.md, GitHubTasks.md, Progress.md, ReviewChecklist.md, and tasks.yml.

Do not add implementation code.
Do not duplicate large sections of the Engineering Handbook.

Run:
- git diff --check
- mkdocs build --strict, if available

Summarize:
- files created or updated
- nav structure
- diagrams added
- GitHub Project workflow assumptions
- verification run
- verification that could not be run
- remaining gaps

Video Creator Example

For Video Creator, use:

Placeholder	Value
`[Product Name]`	`Anuva Video Creator`
`[product-main-repository]`	`anuva-main-video-creator`
`[implementation-repository-1]`	`anuvax-cms`
`[implementation-repository-2]`	`anuva-python-server`
`[implementation-repository-3]`	`anuva-unity-video-creator`

Keep the generated repository focused on product coordination. Web, Python, and Unity implementation details remain in their owning repositories.