project-planner
Scannednpx machina-cli add skill aiskillstore/marketplace/project-planner --openclawProject 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
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xdarkmatter/project-planner/SKILL.mdView on GitHub Overview
The Project Planner skill acts as a lightweight awareness layer for docs/PLAN.md. It detects when plans need attention—missing, stale, or out-of-date—and points users to the appropriate session commands. It never edits plans directly; all changes go through /save and /sync.
How This Skill Works
It scans docs/PLAN.md for presence and freshness, applying staleness heuristics to flag missing, stale, or uncommitted work. It surfaces suggested session commands such as /save to create, refresh, or review the plan. It never modifies the plan itself, only guides what to run.
When to Use It
- No plan exists
- Plan is stale
- Need to see plan
- Update progress
- Start fresh
Quick Start
- Step 1: If there is no PLAN.md, run /save 'initial goals' to create it.
- Step 2: If the plan is stale, refresh with /sync --git.
- Step 3: Periodically review with /sync --status or update via /save 'notes'.
Best Practices
- Keep docs/PLAN.md as the single source of truth.
- When missing, create the initial plan with /save.
- Refresh plan state with /sync --git for recent commits.
- Review current plan with /sync --status before updates.
- Use /save (or /save 'notes') to persist progress and /save --archive to start anew.
Example Use Cases
- A team discovers docs/PLAN.md is missing and uses /save to create it.
- Plan is stale after several days with git activity; /sync --git is suggested.
- Uncommitted work is visible: git status shows modified files and /sync --status is recommended.
- Resuming a project triggers a session start and /sync to restore state.
- Starting fresh: the team archives the old plan with /save --archive.
