pi-planning-with-files

Store planning artifacts in task_plan.md, findings.md, and progress.md files.

26.1k|2.2k|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/OthmanAdi/planning-with-files --skill pi-planning-with-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-planning-with-files
Source: https://github.com/OthmanAdi/planning-with-files/tree/main/.pi/skills/planning-with-files
Command: npx skills add https://github.com/OthmanAdi/planning-with-files --skill pi-planning-with-files

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Planning complex multi-step tasks often loses context as RAM is limited; this skill stores core planning artifacts on disk (task_plan.md, findings.md, progress.md) to keep state between sessions and enable reliable recovery.

Core Features & Use Cases

  • Three-file planning pattern (task_plan.md, findings.md, progress.md) that separates plan, research, and progress.
  • Session recovery and context restoration from previous planning data to resume work after breaks.
  • Ready-to-use templates and scripts to bootstrap projects and maintain a persistent knowledge base.

Quick Start

Create a new planning session by initializing the planning files in your project: task_plan.md, findings.md, and progress.md.

Frequently Asked Questions about pi-planning-with-files

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

FAQPage Schema
How do I maintain task planning context for complex multi-step projects across sessions?

Maintain task planning context across sessions by storing core artifacts on disk using a three-file pattern: task_plan.md, findings.md, and progress.md. This separates planning, research, and progress to preserve state reliably.

What is the best way to recover an AI agent session after a break in a multi-step project?

Recover an AI agent session by restoring context from previously saved planning data on disk. The three-file pattern of task_plan.md, findings.md, and progress.md enables reliable session recovery and immediate work resumption.

How do I start a persistent markdown planning workspace for task orchestration?

Start a persistent markdown planning workspace by initializing the three required files in your project directory: task_plan.md, findings.md, and progress.md. Ready-to-use templates and scripts bootstrap the session and guide execution.

Can I use markdown files for memory management in research tasks instead of relying on RAM?

Yes, you can use markdown files for memory management in research tasks. Storing planning artifacts on disk bypasses limited RAM constraints, creating a persistent knowledge base that tracks findings and progress reliably.

Do I need any external dependencies to implement persistent task planning with markdown?

No external dependencies are required to implement persistent task planning with markdown. The skill operates independently using standard markdown files and accompanying scripts to manage templates, execution, and session recovery.

When should I not use a disk-based file pattern for AI agent task planning?

Disk-based file pattern task planning is unnecessary for simple, single-step tasks that fit entirely within active memory. It is designed specifically for complex multi-step projects, research tasks, and orchestration requiring session recovery.