project-planner

Project plan staleness is detected by monitoring docs/PLAN.md modification times against recent git activity. When your repository shows new commits but the plan hasn't been updated, the Skill flags it as stale and recommends running the /plan command to refresh your planning.

If docs/PLAN.md doesn't exist in your repository, the Skill detects this gap and suggests using the /plan command to create one. This ensures your project workflow has a documented plan to track against.

Workflow automation for project planning works by continuously observing your plan file and git history. The Skill automatically identifies when you have uncommitted work or stale plans, then surfaces concrete /plan command recommendations to keep your workflow synchronized.

The Skill specifically monitors docs/PLAN.md presence and timestamps within your repository. It's designed for workflows using this standard documentation path; repositories with alternative plan storage may need plan migration to benefit from automatic detection.

The /plan command is the suggested action when the Skill detects missing or stale plans. It's the concrete step to update your project documentation and re-align your plan with current git activity and uncommitted work.