Plan Index Manager
> Automatically maintain an organized index of your Claude Code planning files
Best use case
Plan Index Manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
> Automatically maintain an organized index of your Claude Code planning files
Teams using Plan Index Manager should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
How Plan Index Manager Compares
| Feature / Agent | Plan Index Manager | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
> Automatically maintain an organized index of your Claude Code planning files
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Plan Index Manager > Automatically maintain an organized index of your Claude Code planning files ## Overview Plan Index Manager is a Claude Code hook that automatically scans your `~/.claude/plans/` directory and generates a searchable INDEX.md file. It extracts metadata from each plan file (date, title, priority, status) and organizes them in a clean, sortable table. ## Features - đ **Auto-sync on PlanModeEnd** - INDEX.md updates automatically when you exit Plan Mode - đ **Bilingual Support** - Switch between English and Chinese templates - đ **Smart Metadata Extraction** - Automatically detects plan priority and status - đïž **Priority Grouping** - Plans organized by P0/P1/P2 priority levels - đ **Easy Search** - Quickly find plans by keywords - ⥠**Manual Trigger** - Run `bash ~/.claude/hooks/plans-sync.sh` anytime ## Installation ```bash # Download and install curl -fsSL https://raw.githubusercontent.com/flyzhenghao/plan-index-manager/main/install.sh | bash # Or clone and install manually git clone https://github.com/flyzhenghao/plan-index-manager.git cd plan-index-manager bash install.sh ``` ## Usage ### Automatic (Recommended) The INDEX.md will be automatically updated every time you exit Plan Mode in Claude Code. ### Manual ```bash # Sync plans manually bash ~/.claude/hooks/plans-sync.sh # Switch language to Chinese bash ~/.claude/hooks/plans-sync.sh --lang zh # Switch language to English bash ~/.claude/hooks/plans-sync.sh --lang en ``` ### Querying Plans Once installed, you can ask Claude Code: - "æ„èŻą Plan: mobile UI" - Search for plans related to mobile UI - "æąć€ Plan: Authentication System" - Restore a specific plan by title ## Configuration Language setting is stored in `~/.claude/hooks/plans-sync-config.sh`: ```bash # Supported: en, zh PLAN_INDEX_LANG="en" ``` ## Metadata Detection The script automatically extracts: - **Date**: File modification time - **Title**: First `# ` heading (strips "Peer Review Report:" prefix) - **Priority**: Searches for P0/P1/P2 in content (defaults to P1) - **Status**: Detects keywords like "completed", "in progress", "planning", "ongoing" ## Requirements - Claude Code installed - Bash 4.0+ - Plans directory at `~/.claude/plans/` ## License MIT ## Contributing Contributions are welcome! Please feel free to submit a Pull Request. ## Author Created by the Claude Code community
Related Skills
netops-asset-manager
Manage IT infrastructure assets (routers, switches, servers, GPU clusters) through a Go + Vue 3 platform with real-time health probing, SSH remote control, configuration backup, bulk import, network topology visualization, and PM2 process management. Supports H3C, Huawei, Cisco, MikroTik, Ruijie, DCN, and Linux. Use when the user asks about IT asset management, network device operations, infrastructure monitoring, SSH device control, or development on this Go + Vue 3 platform.
You are a professional Chief Marketing Officer. Your task is to help a user start and grow their social media presence organically through a series of questions and generate a growthplan.md blueprint.
Follow these instructions:
plan-writing-gherkin-criteria
Guide for writing Gherkin acceptance criteria using Given-When-Then syntax for testable requirements. Covers scenario structure, background blocks, scenario outlines with examples tables, common patterns for authentication/CRUD/validation/error handling, and best practices for clear testable specifications. Essential for writing user stories and plan acceptance criteria
plan-creating-project-plans
Comprehensive project planning standards for plans/ directory including folder structure (ideas.md, backlog/, in-progress/, done/), stage-aware naming convention (backlog/done use YYYY-MM-DD__identifier/, in-progress uses identifier/ with no date prefix), five-document file organization (README.md, brd.md, prd.md, tech-docs.md, delivery.md for multi-file default; single README.md for trivially-small single-file exception), BRD/PRD content-placement rules, Gherkin acceptance criteria, and the mandatory structured multiple-choice grilling gates (pre-write and post-write) for resolving design decisions with the user. Essential for creating structured, executable project plans.
cw-plan
Transforms a specification into a task graph with dependencies. This skill should be used after cw-spec to break a spec into executable tasks with proper sequencing before dispatching with cw-dispatch.
~aod-project-plan
Validates architecture documentation completeness by checking for technology stack, API specifications, database schema, security architecture, and alignment with feature specification. Use this skill when you need to check if plan.md is complete before implementation, validate architecture documentation, or review technical plans for completeness.
~aod-plan
Plan stage orchestrator that runs all three Plan sub-steps (spec â project-plan â tasks) in sequence with governance gates. Stops on rejection, continues through approvals. Use this skill when you need to run the full Plan stage, navigate planning sub-steps, or resume after a rejection.
plan-with-team
Validate plan file ownership
plan-design-review
Review implementation plans and specs for design quality before coding. Use when a plan needs UI/UX critique, missing state coverage, AI-slop detection, responsive/accessibility checks, or unresolved design decisions.
plan
Plan mode for Hermes Agent â inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.
flow-planning
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
plan-phase
Produce an executable plan for a bounded slice or phase.