pm-update

To update project management config files after restructuring, rescan the repository to regenerate Infrastructure and Architecture sections while preserving user-edited sections like Role and OKRs. A depth-2 directory scan detects deployment signal files, produces a diff for review, and writes updates after explicit confirmation.

Keeping PM configuration in sync involves re-scanning the repository to detect deployment and service signal files, then regenerating the Infrastructure and Architecture sections. Manual project metadata like Workflow Rules and Team sections are preserved verbatim so they do not drift from the codebase.

Architecture detection works by performing a depth-2 directory scan to find deployment and service signal files, extracting key dependency and environment clues. This identifies new service integrations and updates the PM configuration with accurate infrastructure metadata.

Yes, you can review config changes before they are written. The review-first workflow generates a clear diff of proposed changes to the pm-config.md file and requires explicit user confirmation before writing any updates to the repository.

You need to rescan your repository to update infrastructure metadata after major milestones, new service integrations, or large directory restructures. This ensures PM guidance, onboarding notes, and operational rules remain accurate and actionable.

During a repository diff review, user-edited sections including Role, OKRs, Workflow Rules, Dependency Rules, Team, and Notes are preserved verbatim. Only the Infrastructure and Architecture sections are regenerated from the detected deployment and service signal files.