Best Practices
- 1Always invoke Pearl_PM at session start before opening any lane
- 2Pass it the current branch name and last closed PR so it can detect collisions
- 3Trust its routing — if it says a lane is blocked, don't open it anyway
- 4If two sessions need the same file, let Pearl_PM assign write-scope locks
- 5Use it to log operator decisions as OPD rows in ACTIVE_WORKSTREAMS.tsv
CLI Examples
# Start of every session act as pearl_pm # Check what's highest priority pearl_pm: what's the next open workstream? # Log a decision pearl_pm: log OPD — decided to freeze audiobook pipeline until zh-TW coverage closes # Collision check before opening a lane pearl_pm: I'm about to open a lane touching lean_book_pipeline.py — any collisions?
Do Not Use For
- Executing the work — Pearl_PM routes, it doesn't build
- Replacing Piper — Pearl_PM routes sessions, Piper routes prompts
- Being skipped — collisions that Pearl_PM would have caught cost hours to unwind