planning-with-files-zh

Organize multi-step projects by maintaining task_plan.md, findings.md, and progress.md files.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/binfen1/my-skills --skill planning-with-files-zh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-with-files-zh
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/planning-with-files-zh
Command: npx skills add https://github.com/binfen1/my-skills --skill planning-with-files-zh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

这项技能通过持久化的规划文件帮助团队在跨会话情境中组织和跟踪多步骤任务的进度。

Core Features & Use Cases

  • 自动创建和维护 task_plan.md、findings.md 和 progress.md,以记录阶段、决策和结果。
  • 支持在复杂任务中按阶段推进、读取前一会话的上下文,并在需要时恢复会话。
  • 为长期研究或项目提供一致的工作流和版本化的计划。

Quick Start

Create task_plan.md, findings.md, and progress.md in your project root to begin planning and then update findings.md as you research.

Frequently Asked Questions about planning-with-files-zh

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

FAQPage Schema
How do I track multi-step project planning across multiple sessions?

Maintain persistent planning files like task_plan.md, findings.md, and progress.md to track multi-step project phases, decisions, and results across multiple sessions. This workflow enforces early plan creation, reads prior context before tool use, and provides recovery hooks for seamless session continuation.

What is the best way to recover context for long-running research tasks?

Recover context for long-running research tasks by reading structured markdown planning files that document previous phases and findings. The workflow implements explicit statuses and recovery hooks, allowing you to resume complex research exactly where the previous session left off without losing track of decisions or results.

How do I organize complex task planning with persistent file memory?

Organize complex task planning with persistent file memory by automatically creating and updating task_plan.md, findings.md, and progress.md in your project root. These files track explicit workflow phases and statuses, enforcing early plan creation and ensuring all tool invocations reference documented decisions and context.

Do I need to manually create planning files before starting a multi-step workflow?

You do not need to manually create planning files before starting a multi-step workflow, as the process enforces early plan creation and automatically maintains task_plan.md, findings.md, and progress.md. Simply begin planning in your project root, and the files will be generated and updated as you research and progress through phases.

Why does my complex project workflow lose track of decisions during context switching?

Complex project workflows lose track of decisions during context switching when they lack persistent file memory. By enforcing a structured workflow that reads planning files before tool use and records outcomes in findings.md and progress.md, all decisions and phases are preserved across context switches and long-running sessions.

Can I use markdown files for project management in long-running work?

You can use markdown files for project management in long-running work by maintaining task_plan.md, findings.md, and progress.md to track phases, decisions, and results. This provides a consistent, versioned planning workflow that supports multiple tool invocations and session recovery for complex tasks.