project-planner

Detect stale project plans by checking the last-modified date of docs/PLAN.md against recent git activity. This identifies when your planning docs need attention and points to the appropriate session commands.

Maintain a single source of truth for project planning by storing plans in docs/PLAN.md. The system checks for this file's existence and guides you through status checks and updates without modifying the plan directly.

Update your project plan by issuing the /save command to create or update docs/PLAN.md. The system then suggests appropriate session commands like /save and /sync to keep your planning workflow current.

Check docs/PLAN.md status without modifications by detecting file existence and evaluating staleness via git activity. The system guides you to relevant commands like /save and /sync without performing any file modifications.

Staleness detection relies on git activity to identify when plans need attention. Without git activity data, the system can still check for the existence of docs/PLAN.md but cannot fully assess plan staleness.

Sync project planning docs when staleness is detected through last-modified dates and git activity. The system points you to the /sync command to ensure your docs/PLAN.md remains current with recent project changes.