planning-with-files-zh
Installation
Summary
Manus-style file-based planning system for organizing and tracking multi-step project progress.
- Creates three persistent markdown files—task_plan.md, findings.md, and progress.md—that serve as disk-based working memory across sessions
- Automatically detects and loads active plans on each prompt, with tamper detection and attestation to prevent injection attacks
- Includes session recovery via catchup script to restore context from previous interrupted work and sync untracked changes
- Supports scoped plans (nested in .planning/ directories) and root-level plans, with clear rules for when to read, write, and update each file
- Provides templates, error tracking matrices, and a three-failure protocol to prevent repeated mistakes and guide decision-making before major actions
SKILL.md
Contains Hooks
This skill uses Claude hooks which can execute code automatically in response to events. Review carefully before installing.
文件规划系统
像 Manus 一样工作:用持久化的 Markdown 文件作为你的「磁盘工作记忆」。
第一步:恢复项目状态
继续之前,先解析属于此任务的计划目录:
- 使用已安装的
scripts/resolve-plan-dir.sh(或.ps1),结合该主机的PLAN_ID和PWF_PLAN_ROOT,从这一个选定目录读取task_plan.md、progress.md和findings.md。 - 如果显式选择器被拒绝,或会话隔离已启用且存在多个计划但没有
PLAN_ID,请修正固定关系,不要回退到另一项任务。只有没有适用的选择器或命名计划时,才使用项目根目录的旧文件。 - 运行
git diff --stat,确认尚未记录的代码变更。
下文所有规划文件名都指向这个选定目录。并行任务时,在启动每个主机前固定它,或使用独立工作树;在子进程中导出变量不会改变主机环境。一个协调者拥有共享计划和摘要,工作者使用分配的文件或账本。
自动恢复到此为止。无参数运行 session-catchup.py 以及生命周期钩子都不会检查代理的会话存储。只有在用户明确要求查阅本机会话历史时,才选择以下模式之一:
Installs
18.1K
Repository
othmanadi/plann…th-filesGitHub Stars
27.3K
First Seen
Mar 19, 2026
Security Audits