project-lifecycle

You can automate project lifecycle management by using orchestration tools that initialize git repositories, generate context files under .claude/context/projects, register projects in paths-registry.yaml, and handle consolidation and archival to maintain traceability across multiple software projects.

The best way to register existing projects is to add them to a paths-registry.yaml file and generate corresponding per-project context files. This allows you to maintain cross-project context and track priorities for ongoing management and collaboration across teams.

You keep project context files updated through a consolidation process that syncs knowledge, updates documentation, and commits changes to the project state. This maintains accurate per-project context under .claude/context/projects for ongoing traceability.

Yes, this project orchestration approach works for multiple projects by tracking them all in paths-registry.yaml and maintaining individual context files under .claude/context/projects. It supports cross-project context management and priority tracking for cross-team collaboration.

Before initializing new projects, you need a projects_root directory configured for creation, and a paths-registry.yaml file to track registrations. The setup process will handle git initialization, README generation, and .claude/CLAUDE.md context file creation automatically.

You should archive a project in a lifecycle management workflow after consolidation is complete—meaning knowledge has been synced, documentation updated, and changes committed. Archival is the final stage that ensures all project context is preserved for future traceability.