update-codex-documentation

name	update-Codex-documentation
description	Update project documentation files (README.md, PROJECT_BRIEF.md, TECH_STACK.md, ARCHITECTURE.md, docs/API.md, docs/DATABASE.md, AGENTS.md) when significant changes occur. Use for feature additions, architecture changes, dependency updates, API/database modifications. Ensures consistency across all docs.

Update Codex Documentation

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Use when

• The task matches this domain: "Update project documentation files (README.md, PROJECT_BRIEF.md, TECH_STACK.md, ARCHITECTURE.md, docs/API.md, docs/DATABASE.md, AGENTS.md) when significant changes occur. Use for feature additions, architecture changes, dependency updates, API/database modifications. Ensures consistency across all docs."
• The user needs repo-maintenance or skill-authoring support rather than project output.

Do not use when

• A build, writing, or audit skill should own the task instead.
• There is no repository or skill-maintenance action to perform.

Required inputs

• The files, changes, or workflow that need maintenance.
• Current repository conventions and any behavior that must not regress.

Workflow

1. Read the current repository state and the exact maintenance goal.
2. Use the preserved guidance and any bundled scripts to perform the minimum effective change.
3. Keep the result aligned with existing repo conventions.
4. Prepare the output so a follow-on safety review or documentation pass is straightforward.

Quality standards

• Maintenance changes must reduce ambiguity, not add process noise.
• Outputs should preserve portability and existing behavior.
• The result should be easy for another agent to continue using.

Anti-patterns

• Do not introduce product-specific assumptions into portable skill rules.