Agent Plugins Marketplace
All plugins

plan

v1.0.0

Lightweight markdown-based tracker for bugs, features, chores, and todos that lives in docs/plan/ inside your repo

CodexClaude Code5 Skills

By mikersays0 GitHub starsUpdated 4 days ago

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
5 skill or MCP entries
Source updated
Sep 19, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology

Install plan for Codex and Claude Code

Installs for the current user
codex plugin marketplace add mikersays/mikersays-plugins
codex plugin marketplace upgrade mikersays-plugins
codex plugin add plan@mikersays-plugins

Paste and run these commands in a terminal with Codex. They add and refresh the mikersays-plugins catalog, then install this plugin.

Compatibility: the page URL and API slug “plan-5” remain stable.

  • Codex: plan-5@agent-plugin-marketplaceplan@mikersays-plugins

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mikersays/mikersays-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/plan/.

Plugin files

plugins/plan/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/plan-add/SKILL.md
├── skills/plan-close/SKILL.md
├── skills/plan-init/SKILL.md
├── skills/plan-list/SKILL.md
└── skills/plan-update/SKILL.md

Included Skills5

plan-addskills/plan-add/SKILL.md

Create a new planning item (bug, feature, chore, or todo) as a markdown file inside docs/plan/. Use this whenever the user wants to track a new bug, feature, todo, follow-up, issue, or piece of deferred work in their repo — including phrases like "log this", "track this", "remember to", "I need to fix", "add this to the plan", or any "we should do X later" request. Auto-initializes docs/plan/ if it doesn't exist yet.

plan-closeskills/plan-close/SKILL.md

Close (mark done) a planning item in docs/plan/. Use whenever the user finishes work on a tracked bug/feature/chore/todo — phrases like "I fixed it", "that's done", "ship that off", "close item 7", "mark X complete", "wrap up the search ticket" all trigger this. Sets status to done and stamps the closed date. The file is not deleted or moved — closed items stay in docs/plan/ as the history record.

plan-initskills/plan-init/SKILL.md

Bootstrap a docs/plan/ folder in the current repo for tracking bugs, issues, chores, and todos as markdown files. Use this whenever the user wants to start a lightweight planning system, set up local issue tracking inside a repo, or asks for a "plan folder" / "todo tracker" / "issues directory" — even before they've used any other /plan-* command. /plan-add also auto-inits if the folder is missing.

plan-listskills/plan-list/SKILL.md

List planning items in docs/plan/, optionally filtered by status, type, priority, due date, or tag. Use whenever the user wants to see open issues/bugs/todos, check the status of planned work, find overdue items, or get an overview of what's in the plan folder. Phrases like "what's open", "what's due", "show me bugs", "list todos", "what's in the plan", "show overdue work" all trigger this. The default view hides done items.

plan-updateskills/plan-update/SKILL.md

Update an existing planning item in docs/plan/ — change its status, priority, due date, type, tags, or append a dated note. Use whenever the user wants to mark something in-progress, change a deadline, raise/lower priority, unblock something, retitle, or add a comment/note to a tracked item. Accepts either the numeric ID or a slug fragment from the title. Phrases like "start work on 7", "push X to next week", "mark item Y blocked", "add a note to the search ticket" all trigger this.

Plugin manifests2

plugins/plan/.codex-plugin/plugin.json
{
  "name": "plan",
  "description": "Lightweight markdown-based tracker for bugs, features, chores, and todos that lives in docs/plan/ inside your repo",
  "version": "1.0.0",
  "skills": "./skills/",
  "interface": {
    "displayName": "Plan",
    "shortDescription": "Lightweight markdown tracker for bugs, features, and todos",
    "category": "Productivity"
  }
}
plugins/plan/.claude-plugin/plugin.json
{
  "name": "plan",
  "description": "Lightweight markdown-based tracker for bugs, features, chores, and todos that lives in docs/plan/ inside your repo",
  "version": "1.0.0",
  "author": {
    "name": "mikersays"
  }
}

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[plan on Agent Plugins Marketplace](https://pluginsmp.com/plugins/plan-5)