update-project-memory

Intelligently update project documentation to reflect current Orchestre capabilities. This prompt analyzes existing documentation and adds or updates Orchestre-specific sections while preserving all user content.

Overview

The /update-project-memory prompt solves a common problem: projects that are partially initialized or have outdated Orchestre documentation. It intelligently reads existing files, identifies what's missing or outdated, and updates them to reflect the current state of Orchestre - all while preserving user customizations.

Usage

/update-project-memory [focus]

Arguments

Argument	Required	Description
focus	No	Specific files to update (defaults to all: CLAUDE.md, README.md, .orchestre/*)

Examples

Update All Documentation

/update-project-memory

Updates all project documentation files to current Orchestre state.

Focus on Specific Files

/update-project-memory "CLAUDE.md and README.md only"

Updates only the specified files.

What Gets Updated

CLAUDE.md (Root)

Adds or updates the "Powered by Orchestre" section with:

• Current tool and prompt counts (8 tools, 20 prompts, 50 template commands)
• Available commands overview
• Getting started guide
• Link to documentation

README.md

Adds or updates the "Orchestre Commands" section with:

• Brief mention of Orchestre integration
• Key commands for the project
• Link to full command list

.orchestre/CLAUDE.md

Updates with:

• Current version numbers
• Correct tool/prompt counts
• New features and capabilities

.orchestre/prompts.json

Ensures the configuration includes:

• All 20 essential prompts
• Template-specific prompts
• Current version

Update Process

1. Analysis Phase

   • Reads all relevant documentation files
   • Identifies missing Orchestre sections
   • Detects outdated information (wrong counts, old versions)

2. Planning Phase

   • Creates a plan for updates needed
   • Determines optimal placement for new sections
   • Identifies content to preserve

3. Update Phase

   • Adds missing sections
   • Updates numbers and versions
   • Preserves all user content
   • Ensures consistency across files

4. Summary Phase

   • Reports what was changed
   • Highlights any issues found
   • Suggests next steps

Common Updates

From v5.3.0 to v5.3.1

• Updates from 19 to 20 essential prompts
• Updates from 9 to 8 MCP tools
• Adds mention of /update-project-memory command

Missing Sections

• Adds "Powered by Orchestre" to CLAUDE.md
• Adds "Orchestre Commands" to README.md
• Creates .orchestre/CLAUDE.md if missing

Outdated Information

• Fixes old version numbers
• Updates tool/prompt counts
• Refreshes command lists

Best Practices

When to Use

✅ Use this prompt when:

• Project was partially initialized
• Documentation has outdated Orchestre information
• CLAUDE.md is missing Orchestre sections
• Tool/prompt counts are wrong
• After updating Orchestre version

❌ Don't use when:

• Creating a new project (use /create)
• Documentation is already up-to-date
• You want to remove Orchestre references

Preserving User Content

The prompt is designed to:

• Never remove user-written sections
• Add new content in logical places
• Merge updates intelligently
• Respect existing formatting

Version Accuracy

Always uses:

• Current Orchestre version
• 8 MCP tools
• 20 essential prompts
• 50 template commands

Integration with Other Commands

Works well with:

• /status - Check project state before updating
• /discover-context - Understand project before updates
• /initialize - For adding Orchestre to projects

Example Workflow

# 1. Check current project status
/status

# 2. Update documentation
/update-project-memory

# 3. Verify updates
cat CLAUDE.md | grep "Powered by Orchestre"

Troubleshooting

"No Orchestre sections found"

This is normal for projects without Orchestre documentation. The prompt will add all necessary sections.

"Conflicting information detected"

The prompt found inconsistent information across files. It will standardize to current values.

"User customizations preserved"

This message confirms that existing user content was kept intact while adding Orchestre sections.

Related Resources

• Project Memory System - Understanding distributed memory
• Memory System - Documentation structure
• /update-memory - Update memory with discoveries

Version History

• v5.3.1: Initial implementation of update-project-memory prompt
  • Intelligent content analysis and updates
  • Preservation of user content
  • Support for all documentation files