GitHub Project Workflow

The Anuva Video Creator GitHub Project is the execution tracking layer between product-main planning and repository implementation.

anuva-main-video-creator owns product feature docs, repository impact, task creation, progress sync, and product review. Implementation repositories own the code, local docs, tests, PRs, and completion reports.

flowchart TD
    Idea["Feature request"]
    Docs["FeatureBrief.md and RepositoryImpact.md"]
    Tasks["tasks.yml and HandoffPrompts.md"]
    Issues["Implementation repository issues"]
    Project["Anuva Video Creator GitHub Project"]
    Repo["Implementation repository work"]
    PR["PR completion report"]
    Progress["GitHubTasks.md and Progress.md"]
    Publish["anuva-dev-docs refresh"]

    Idea --> Docs
    Docs --> Tasks
    Tasks --> Issues
    Issues --> Project
    Project --> Repo
    Repo --> PR
    PR --> Project
    Project --> Progress
    Progress --> Publish

Product Change Folder

Cross-repository Video Creator features should use:

docs/changes/<YYYY-MM-DD-feature-name>/
  BrainDump.md
  FeatureBrief.md
  RepositoryImpact.md
  HandoffPrompts.md
  GitHubTasks.md
  Progress.md
  ReviewChecklist.md
  tasks.yml

File	Purpose
`BrainDump.md`	Raw feature notes, user intent, constraints, and unresolved thinking.
`FeatureBrief.md`	Product goals, non-goals, user impact, acceptance criteria, and behavior.
`RepositoryImpact.md`	Affected repositories, ownership boundaries, sequencing, docs impact, and verification expectations.
`HandoffPrompts.md`	Human-readable prompts for each implementation repository.
`GitHubTasks.md`	Issue links, project item status, PR links, verification, docs impact, and product review status.
`Progress.md`	Product-level implementation progress grouped by repository.
`ReviewChecklist.md`	Product integration review before the feature is complete.
`tasks.yml`	Machine-readable task definitions for issue creation and project field updates.

Issue Body Shape

Each implementation issue should include enough context for Codex to work inside the owning repository without hidden chat memory.

Product Feature ID:

Product Source:

Repository:

Task Summary:

Product Context:

This Repository Owns:

This Repository Does Not Own:

Acceptance Criteria:

Docs Impact:

Verification Expectations:

Completion Report Required:

Project Fields

Field	Example Values	Purpose
`Status`	Backlog, Ready, In Progress, In Review, Done, Blocked	Kanban state for the task.
`Repository`	`anuvax-cms`, `anuva-python-server`, `anuva-unity-video-creator`, `anuva-main-video-creator`	Owning repository.
`Feature ID`	`2026-07-05-shot-template-library`	Links all tasks for one feature.
`Product Change Folder`	`docs/changes/2026-07-05-shot-template-library`	Points back to product-main docs.
`Priority`	High, Medium, Low	Helps sequence implementation.
`Docs Impact`	None, Local, Product, Handbook, Publisher	Signals documentation work required.
`PR`	Pull request URL or number	Connects task tracking to implementation.
`Verification`	Pending, Passed, Skipped, Failed	Summarizes local verification state.

Product-Main Sync

GitHubTasks.md should track issue and project state in a compact table:

| Repository | Issue | Project status | PR | Verification | Docs impact | Product review |
| --- | --- | --- | --- | --- | --- | --- |
| `anuvax-cms` | `#123` | In Review | `#130` | Passed | Local | Pending |
| `anuva-python-server` | `#88` | In Progress | - | Pending | Local | Pending |
| `anuva-unity-video-creator` | `#52` | Done | `#57` | Passed | Local | Accepted |

Progress.md should summarize the human-readable state, product risks, blocked decisions, and release readiness.

Completion Report

Implementation PRs should include:

Product Feature ID:
Product Change Folder:
GitHub Issue:
Repository:

Implementation Summary:

Docs Updated:

Verification Run:

Verification Skipped:

Integration Notes for anuva-main-video-creator:

Open Questions:

Follow-ups:

Publishing

When product-main docs, implementation docs, or GitHub Project status output changes, trigger or record the required anuva-dev-docs refresh. The publisher owns generated static output; this repository owns the source product docs.

Completion Criteria

The workflow is complete for a feature when:

product-main feature docs can be traced to implementation issues
implementation issues appear in the Anuva Video Creator GitHub Project
PRs link back to the product feature and include completion reports
GitHubTasks.md and Progress.md match issue, PR, and project state
verification and docs impact are recorded for each repository
release notes, change history, and publishing refresh notes are updated