Project planner
Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill project-plannerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things 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.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
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, 434 tokens by cl100k_base, 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
What ships with it: 1 file
21.8 KB alongside SKILL.md
- skill-report.json21.8 KB
Gives 0 of the 12 instructions most plan spec skills give in 434 tokens
Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06
- Ask one question at a timein 73 of 1360
- Write the spec using the templatein 22 of 1360
- Ask clarifying questions if neededin 19 of 1360, across 18 files
- Wait for user confirmation before proceedingin 19 of 1360
- Save plans to the plans directoryin 17 of 1360, across 13 files
- Check for product marketing context firstin 16 of 1360, across 5 files
- Read the plan file completelyin 16 of 1360
- Order tasks by dependencyin 16 of 1360
- Gather context from the conversationin 15 of 1360, across 9 files
- Explore the codebase instead of askingin 15 of 1360, across 13 files
- Wait for explicit user approvalin 14 of 1360, across 13 files
- Quiz the user on the breakdownin 13 of 1360, across 7 files
Said here and by no other author read
- Detect when plan files are missing
- Identify stale project plans
- Suggest appropriate session commands
- Suggest save to create initial plans
- Suggest sync --git to update plans
- Suggest sync --status to review
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.