From claude-mods
Detects missing or stale docs/PLAN.md project plans via git activity and status, suggesting /save and /sync commands for updates and progress tracking.
npx claudepluginhub 0xdarkmatter/claude-modsThis skill is limited to using the following tools:
Lightweight awareness layer for `docs/PLAN.md`. Detects when plans need attention and points to `/save` and `/sync` commands.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Lightweight awareness layer for docs/PLAN.md. Detects when plans need attention and points to /save and /sync commands.
This skill does NOT manage plans directly. It:
docs/PLAN.md exists or is missingAll plan operations go through /save (persist) and /sync (restore/status).
No docs/PLAN.md found
-> Suggest: /save to create initial plan from conversation
docs/PLAN.md last modified: 5 days ago
git log shows: 12 commits since then
-> Suggest: /sync --git to update from commits
git status shows: 5 modified files
docs/PLAN.md "In Progress" section outdated
-> Suggest: /sync --status to review
Resuming work on project with docs/PLAN.md
-> Suggest: /sync to restore state
| Situation | Suggestion |
|---|---|
| No plan exists | /save after discussing goals |
| Plan is stale | /sync --git |
| Need to see plan | /sync --status |
| Update progress | /save "notes" |
| Start fresh | /save --archive |
A plan is considered stale when:
A plan needs review when:
/sync reads state, /save writes statedocs/PLAN.md