Skip to content

Prompt: Plan Cross-Repository Feature

Use this prompt in the repository that owns the coordinating decision.

  • Use anuva-engineering-handbook for engineering-wide process, standards, registry, template, prompt, or publishing architecture changes.
  • Use anuva-main-video-creator for Video Creator product features that affect multiple implementation repositories.
Plan this as a cross-repository Anuva feature:

<feature notes>

Use the cross-repository feature workflow.

Create or update a feature plan that includes:

- summary
- goals
- non-goals
- affected capabilities
- affected repositories
- repository-specific responsibilities
- sequencing dependencies
- open questions
- docs impact
- verification strategy
- integration acceptance criteria
- GitHub issue and GitHub Project strategy, if implementation repositories are affected
- anuva-dev-docs publishing impact, if published docs should change

Use the repository registry and capability registry as the routing source of truth.

For Video Creator product features, create or update:

- FeatureBrief.md
- RepositoryImpact.md
- HandoffPrompts.md
- GitHubTasks.md
- Progress.md
- ReviewChecklist.md
- tasks.yml, if GitHub task creation should be automated

Do not implement repository changes. Produce the plan and identify the exact GitHub issues or repository-level tasks that should be created.