How do I install the Project Planner skill?

Run npx skillmds@latest add aiskillstore/project-planner-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Planner safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Planner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Planner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Planner?

aiskillstore (@aiskillstore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Planner by aiskillstore — Agent Skill

Name: Project Planner
Rating: 4.2 (5 reviews)
Author: aiskillstore

File contents

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.md exists 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
/sync reads state, /save writes state
Single source of truth: docs/PLAN.md

---name: project-planner-2description: Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.--- # 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.md` exists 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 - `/sync` reads state, `/save` writes state - Single source of truth: `docs/PLAN.md`

Frequently asked questions

Project Planner