find-plan
Scannednpx machina-cli add skill esimkowitz/claude-plugins/find-plan --openclawFind Plan
Search for and resume work on previously saved plans from .aicontext/ directories. Plans are searched in the current repository first, with fallback to the global ~/.aicontext/ directory.
Workflow Overview
- Search for plans matching user's query
- Present matches and help select the right plan
- Load the plan and set up progress tracking
- Update plan items as work progresses
- Save with updated timestamp when done
Step 1: Search for Plans
Run the search script with the user's query (or no query to list all):
bash ${CLAUDE_PLUGIN_ROOT}/scripts/find-plans.sh "query terms"
Or list all available plans:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/find-plans.sh
The script searches:
- Repository
.aicontext/- Plans saved in current git repo (higher priority) - Global
~/.aicontext/- Plans saved globally (fallback)
Both filename and content are searched. Present the matches to the user with recommendations based on:
- Recency (newer plans more likely relevant)
- Query match quality (filename matches stronger than content matches)
- Context relevance (if in a specific project, prefer repo plans)
Step 2: Load Selected Plan
Once the user confirms which plan to resume:
- Read the full plan file using the Read tool
- Identify actionable items in the plan (checkboxes, numbered steps, task lists)
- Create TodoWrite entries for trackable items to maintain visibility
Step 3: Track Progress
As work progresses on plan items, update the plan file to reflect completion status.
For Markdown Checkboxes
Convert unchecked to checked:
- [ ] Task descriptionbecomes- [x] Task description
For Non-Checkbox Items
Append status annotations:
1. Implement auth flowbecomes1. Implement auth flow - COMPLETED- Design database schemabecomes- Design database schema - IN PROGRESS
Use the Edit tool to make these updates incrementally as each task completes.
Step 4: Save Updated Plan
When finishing work or pausing the session, update the plan's date to reflect the latest activity:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/update-plan-date.sh ".aicontext/plan-2025-01-10-feature-name.md"
This renames the file with the current date while preserving the descriptive name, creating a clear timeline of work:
plan-2025-01-10-auth-refactor.md→plan-YYYY-MM-DD-auth-refactor.md(current date)
Example Session
User says: "I want to pick up where I left off on the auth work"
-
Run search:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/find-plans.sh "auth" -
Script outputs matching plans with previews
-
User confirms: "Yes, the auth-session-refactor plan"
-
Read the plan file, create TodoWrite entries for remaining items
-
Work through items, updating checkboxes as completed
-
When pausing or done:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/update-plan-date.sh ".aicontext/plan-2025-12-10-auth-session-refactor.md"
Tips
- If no query is provided, list all plans to help user identify what's available
- Recommend the most likely match based on context, but let user confirm
- Update the plan file frequently to preserve progress
- The date update at the end is important for tracking when work last occurred
- Plans in the current repo's
.aicontext/take priority over global plans
Source
git clone https://github.com/esimkowitz/claude-plugins/blob/main/plugins/save-plan/skills/find-plan/SKILL.mdView on GitHub Overview
Find and resume work on plans stored in .aicontext directories. It searches the current repo first, then falls back to the global store, helping you pick up where you left off and track progress.
How This Skill Works
The skill uses a search script to locate plans, prioritizing repository plans over global ones. After you select a plan, it reads the file, identifies actionable items (checkboxes, numbered steps, and task lists), and creates TodoWrite entries to track progress. As work progresses, it updates plan items (checkboxes or status annotations) and saves a new date when pausing or finishing with update-plan-date.sh.
When to Use It
- Resume a specific plan or pick up where you left off on a saved planning document.
- List or show saved plans to understand what you have in progress.
- Load a saved plan to continue actionable work items on a project.
- Switch context between multiple plans based on project relevance or recency.
- Save progress and update the plan's date after pausing or completing work.
Quick Start
- Step 1: Search for plans using the find-plans script: bash ${CLAUDE_PLUGIN_ROOT}/scripts/find-plans.sh <query terms> or run without a query to list all.
- Step 2: Load the selected plan by reading the plan file and creating TodoWrite entries for remaining items.
- Step 3: Track progress by updating plan items and save the updated date with update-plan-date.sh .aicontext/plan-YYYY-MM-DD-<name>.md
Best Practices
- Prioritize repository .aicontext plans first to ensure the most relevant context.
- Always confirm the plan you want to resume before loading it.
- Review and update actionable items as you complete tasks.
- Use clear status annotations for non-checkbox items to maintain visibility.
- Update the plan date with update-plan-date.sh when pausing or finishing to keep a clear history.
Example Use Cases
- A developer resumes the auth-refactor plan from the repository and creates TodoWrite entries for pending tasks.
- A team lists all available plans with no query to understand which plans exist in the repo and global store.
- A user loads a saved plan, identifies remaining items, and converts them into trackable TodoWrite entries.
- As tasks are completed, checkboxes in the plan are marked, and progress is visible at a glance.
- The session ends and the plan date is updated using update-plan-date.sh to reflect the latest activity.