planning-with-files

Create and maintain task_plan.md, findings.md, and progress.md planning files.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ilderaj/superpowering-with-files --skill planning-with-files-ilderaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-with-files
Source: https://github.com/ilderaj/superpowering-with-files/tree/main/harness/upstream/planning-with-files
Command: npx skills add https://github.com/ilderaj/superpowering-with-files --skill planning-with-files-ilderaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

planning tasks across complex projects often loses goals, context, and phase progress as conversations and tool calls accumulate. This Skill provides a stable on-disk memory by creating and maintaining a task-scoped set of planning files that encode goals, phases, findings, and progress in a durable structure.

Core Features & Use Cases

  • Creates and maintains task_plan.md, findings.md, and progress.md under planning/active/<task-id>/ to track phases, discoveries, and session logs.
  • Supports automatic session recovery and simple companion-sync workflows to coordinate across planning artifacts.
  • Useful for multi-step research, software projects, or any repo-driven task that benefits from an auditable planning trail and easy archiving.

Quick Start

Create an active planning directory for a new task and initiate task_plan.md, findings.md, and progress.md from the templates.

Frequently Asked Questions about planning-with-files

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

FAQPage Schema
How do I persist multi-step task goals and phase progress across tool calls?

Persistent on-disk planning files track multi-step task goals and phase progress by creating task_plan.md, findings.md, and progress.md under a dedicated active planning directory, ensuring context survives across tool calls.

What is on-disk planning memory for software development and research tasks?

On-disk planning memory is a stable set of repository files that maintain durable task state, encoding goals, phases, and findings to provide an auditable planning trail for multi-step development and research workflows.

How do I recover session state for a complex multi-step project after losing context?

Recover session state by reading the persistent progress.md and findings.md files located in the active planning directory, which log discoveries and lifecycle phases to automatically restore task continuity.

Does this persistent task management approach work for cross-tool integration workflows?

Yes, persistent task management works for cross-tool integration by storing durable planning artifacts on disk, allowing various scripts and tools to read or sync task_plan.md and progress.md files within a repository.

When should I use persistent on-disk files instead of in-memory task tracking?

Use persistent on-disk files instead of in-memory tracking when your workflow requires durable state, session recovery, or an auditable planning trail for multi-step research, operations, or software development tasks.