mcpField
P
project-planner

project-planner

github.com/0xdarkmatterAgent workflows7853 installsUpdated 2w ago
Repository

About project-planner

A lightweight agent skill that checks the state of docs/PLAN.md and suggests when to use /save or /sync. It flags missing or stale plans and does not modify them itself.

Key features

  1. 01Detects missing plan files
  2. 02Checks plan staleness against git activity
  3. 03Reviews uncommitted work
  4. 04Suggests /save and /sync commands

Use cases

  1. 01Starting work without a project plan
  2. 02Resuming a project session
  3. 03Reviewing changes against a plan
  4. 04Identifying plans needing updates

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/0xdarkmatter/claude-mods --skill project-planner

After installing, type/project-plannerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
.gitkeep
references/
.gitkeep
scripts/
.gitkeep

Details

From the project README

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

SituationSuggestion
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

Comments

Markdown supported