Project planner
Skill aiskillstore/marketplace/skills/0xdarkmatter/project-planner
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
npx -y skills add aiskillstore/marketplace --skill project-plannerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, as published. Nobody here has run it
Project Planner Skill
Lightweight awareness layer for docs/PLAN.md. Detects when plans need attention and points to /save and /sync commands.
Purpose
This skill does NOT manage plans directly. It:
- Detects when
docs/PLAN.mdexists or is missing - Identifies stale plans (no recent updates vs git activity)
- Suggests appropriate session commands
All plan operations go through /save (persist) and /sync (restore/status).
Detection Logic
Plan Missing
No docs/PLAN.md found
-> Suggest: /save to create initial plan from conversation
Plan Stale
docs/PLAN.md last modified: 5 days ago
git log shows: 12 commits since then
-> Suggest: /sync --git to update from commits
Uncommitted Work
git status shows: 5 modified files
docs/PLAN.md "In Progress" section outdated
-> Suggest: /sync --status to review
Session Start
Resuming work on project with docs/PLAN.md
-> Suggest: /sync to restore state
Quick Reference
| 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 |
Staleness Heuristics
A plan is considered stale when:
- Last modified > 3 days ago AND
- Git shows commits since last modification AND
- Commits relate to plan topics (feat:, fix:, refactor:)
A plan needs review when:
- Session just started
- Significant uncommitted changes exist
- User mentions progress or completion
Notes
- This skill only suggests, never modifies
/syncreads state,/savewrites state- Single source of truth:
docs/PLAN.md