skills.rest
localmin
localminCOMMUNITY
Explore all skills by this author →
Website𝕏@localminGitHub

planning-workflow

Persists plan mode decisions and work-in-progress state in .claude/plans/ markdown documents.

Updated Apr 8, 2017
Search Tags:#workflow#planning#markdown#claude code#session continuity#context persistence#wip tracking
One-click install
npx skills add https://github.com/localmin/dotfiles --skill planning-workflow-localmin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-workflow
Source: https://github.com/localmin/dotfiles/tree/main/coding-agents/skills/planning-workflow
Command: npx skills add https://github.com/localmin/dotfiles --skill planning-workflow-localmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step implementation work loses its requirements, design decisions, and in-progress state when a session ends or context compaction runs, forcing you to re-discuss everything from scratch. ## Core Features & Use Cases - Persistent plan documents: Converts plan mode agreements into structured markdown docs stored under .claude/plans/, indexed via INDEX.md with lazy-read discipline. - WIP.md state snapshots: Captures current task, completed steps, next action, and uncommitted files so interrupted ad-hoc work can resume cleanly. - Session continuity hooks: Uses Claude Code SessionStart and PreCompact hooks to inject WIP state on resume and remind you to flush state before compaction. - Use Case: You agree on a feature design in plan mode, get interrupted mid-implementation, and return days later—the skill's INDEX.md and WIP.md let the agent restate current status and the next step without re-asking settled questions. ## Quick Start Ask the agent to record the agreed plan as a persistent doc in .claude/plans/ and keep WIP.md updated so the work can resume after interruption.

Frequently Asked Questions about planning-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve Claude Code plan mode decisions across sessions?▼

Store the agreed plan as a structured markdown doc in .claude/plans/ and register one line per plan in INDEX.md. On resume, read INDEX.md first and only open the relevant plan doc, so design discussions survive session ends and compaction.

How to resume interrupted work after context compaction in Claude Code?▼

Maintain a WIP.md file in .claude/plans/ recording the current task, completed steps, next action, and uncommitted files. Flush it before compaction and at logical milestones, then read it first when resuming.

Does this planning workflow work with Codex or other CLI agents?▼

The SessionStart and PreCompact hooks are Claude Code specific. For other agents like Codex or Antigravity, follow the same update-timing rules as plain text discipline without hook automation.

Will .claude/plans/ files pollute my git repository?▼

No. The directory is excluded globally via a **/.claude/plans/ entry in ~/.config/git/ignore, so plan docs never appear in commits. Use git add -f only if you explicitly want to share one.

When should I use WIP.md versus a full plan document?▼

Use a plan doc for features whose design was settled in plan mode, one doc per feature. Use WIP.md as a single snapshot of currently in-progress ad-hoc work, and clear it once the task concludes.

Related Skills

Explore More Software Engineering Skills→
MinhDuyDEVMinhDuyDEV

brainstorming

Refine rough ideas into validated software designs with trade-off analysis.

Community
Intermediate
jftecnologiajftecnologia

generate-task-breakdown

Generate development task breakdowns with acceptance criteria from product requirements and architecture documentation.

Official
Advanced
oskar-dragonoskar-dragon

notion-doc

Generate Notion-style PRD documents from design and planning markdown files.

Community
Intermediate
phoenixvcphoenixvc

sync-backlog

Synchronize local backlog items with GitHub or Linear issue trackers.

Official
Advanced