Project Rename

When to Use

When a project needs to be renamed or moved to a different department.

Inputs

• Project path (current): {Dept}/Projects/{OldName}/
• New project name and/or new department

Context Boundary

Read all project files — reference updates require full access.

Prerequisites

• Project must exist on disk and in the sidebar.

Relationship to Project_Complete

Project_Rename is a utility skill for changing a project’s name or department. It does not advance the lifecycle. Use it at any point when a name or location change is needed, including before archiving to resolve name collisions.

Procedure

1. Determine the scope: rename only, move only, or both

2. Rename files: All project files are prefixed with the folder name. Rename every {OldName}_*.md to {NewName}_*.md using git mv

3. Rename folder: git mv the project folder to the new name

4. If moving departments: git mv the folder to {NewDept}/Projects/{ProjectName}/

5. Update internal references: Search all .md files in the project for old name references and update them:

   • Links (markdown links, header table links)
   • Titles (H1 headings)
   • Header tables (owner, project name fields)

6. Update sidebar: Spawn the Page Manager bot via spawnAgent with { botGroup: 'forge', botHandle: 'page-manager' }. If moving departments, relocate the sidebar group.

7. Update external references: Search the repo for links to the old project path and update them:

   grep -rl "old/path" [[orgRepoRoot]]/ --exclude-dir='.internal' --exclude-dir='node_modules' --exclude-dir='.generated' --exclude-dir='dist'

8. Build, commit, push

9. Present the changes to the user for review

10. Iterate until the user approves

Rules

• Always use git mv to preserve history
• File prefix must always match the folder name
• Review all internal links — broken links are the most common rename issue
• Check AGENTS.md and README.md carefully — they often reference the project name