npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@theglitchking/persistent-planning

v1.0.1

Published

Persistent markdown-based planning with task directories, progress tracking, and context engineering for multi-step Claude Code workflows

Downloads

101

Readme

Persistent Planning

Persistent markdown-based planning for Claude Code -- the context engineering pattern pioneered by Manus AI.

A Claude Code plugin that uses on-disk markdown files as "working memory" for planning, progress tracking, and knowledge storage. Plans persist across sessions and support multiple concurrent tasks.

License: MIT Plugin


Why This Plugin?

Claude Code (and most AI agents) suffer from:

  • Volatile memory -- in-memory task tracking disappears on context reset
  • Goal drift -- after 50+ tool calls, original goals get forgotten
  • Hidden errors -- failures aren't tracked, so the same mistakes repeat
  • Context stuffing -- everything crammed into context instead of stored on disk

Persistent Planning solves all of these with the same approach that made Manus AI worth $2 billion: use the filesystem as external memory.

The 3-File Pattern

For every complex task, create three files:

.planning/[task-name]/task_plan.md   -> Track phases and progress
.planning/[task-name]/notes.md       -> Store research and findings
[deliverable].md                     -> Final output

The Loop

1. Create task_plan.md with goal and phases
2. Research -> save to notes.md -> update task_plan.md
3. Read notes.md -> create deliverable -> update task_plan.md
4. Deliver final output

Key insight: By reading task_plan.md before each decision, goals stay in the attention window. This is how Manus handles ~50 tool calls without losing track.

Installation

Option 1: NPM (Recommended)

# Install globally
npm install -g @theglitchking/persistent-planning
persistent-planning install --scope user

# Or via npx (no global install)
npx @theglitchking/persistent-planning install --scope user

Option 2: Installer Script

git clone https://github.com/TheGlitchKing/persistent-planning.git
cd persistent-planning
./install.sh --scope user       # Available in all projects
# OR
./install.sh --scope project    # Current project only

Option 3: Claude Marketplace

/plugin install TheGlitchKing/persistent-planning

Option 4: Manual Installation

mkdir -p ~/.claude/skills
cp -r persistent-planning/skills/SKILL.md ~/.claude/skills/persistent-planning/SKILL.md
cp -r persistent-planning/scripts ~/.claude/skills/persistent-planning/scripts
cp -r persistent-planning/docs ~/.claude/skills/persistent-planning/docs
cp persistent-planning/.claude/commands/start-planning.md ~/.claude/commands/start-planning.md

Usage

Quick Start

/start-planning "Your task name here"

This creates:

.planning/
└── your-task-name/
    ├── task_plan.md    # Track phases and progress
    └── notes.md        # Store research and findings

Session Persistence

Session 1:

/start-planning "Complex feature"
[Work, update plans]

Session 2 (next day):

Read .planning/complex-feature/task_plan.md  <- Plans are still here
Read .planning/complex-feature/notes.md      <- Notes are still here
[Continue work]

Multiple Concurrent Tasks

/start-planning "Refactor authentication"
  -> Creates .planning/refactor-authentication/

/start-planning "Fix memory leak"
  -> Creates .planning/fix-memory-leak/

Each task gets its own directory. No conflicts, no overwrites.

Core Principles

| Principle | Implementation | |-----------|----------------| | Filesystem as memory | Store in files, not context | | Attention manipulation | Re-read plan before decisions | | Error persistence | Log failures in plan file | | Goal tracking | Checkboxes show progress | | Append-only context | Never modify history |

When to Use

Use for:

  • Multi-step tasks (3+ steps)
  • Research tasks
  • Building/creating projects
  • Tasks spanning many tool calls

Skip for:

  • Simple questions
  • Single-file edits
  • Quick lookups

File Structure

persistent-planning/
├── .claude-plugin/
│   └── plugin.json          # Plugin manifest
├── .claude/
│   └── commands/
│       └── start-planning.md    # /start-planning command
├── skills/
│   └── SKILL.md             # Core skill definition
├── scripts/
│   └── init-planning.sh     # Automated setup script
├── docs/
│   ├── reference.md         # Manus context engineering principles
│   └── examples.md          # Worked examples
├── install.sh               # Plugin installer
├── uninstall.sh             # Plugin uninstaller
├── plugin.json              # Root plugin metadata
├── README.md                # This file
├── LICENSE                  # MIT license
└── CHANGELOG.md             # Version history

Cleanup

# Remove a single task's planning files
rm -rf .planning/[task-name]/

# Remove all planning files
rm -rf .planning/

Acknowledgments

  • Manus AI -- for pioneering context engineering patterns
  • Ahmad Othman Ammar Adi (OthmanAdi) -- for the original planning-with-files skill
  • Anthropic -- for Claude Code and the skills framework

License

MIT License -- see LICENSE


Author: TheGlitchKing