planning-with-files-de

Create task_plan.md, findings.md, and progress.md from the skill templates at the start of any complex multi-step project before beginning work
Read existing task_plan.md, progress.md, and findings.md immediately to restore context before taking any action, especially after session compaction or /clear

Hooks reference shell utilities stat, sha256sum/shasum, grep, and sed with platform-specific fallbacks; no guarantee of operation on all environments is documented
Session recovery depends on existence of readable planning files on disk
The source document is truncated mid-table, so the complete read-vs-write decision matrix is not available
Verify task_plan.md exists and has been read before making any decisions on a complex task
Confirm progress.md is updated after every Write or Edit operation, as enforced by the PostToolUse hook
Ensure no phase status in task_plan.md is left stale after phase completion — mark in_progress as complete
If a PLAN TAMPERED message appears, stop and either run /plan-attest to re-approve the file or restore it from git before continuing
After session compaction (PreCompact hook fires), confirm progress.md captures all recent actions and task_plan.md status reflects the current phase

AI 搜索