task-externalization
将大型任务上下文外部化到.scratch/tasks/文件中的系统,以在上下文压缩和会话重置之间保持连续性。当开始大型/复杂任务后、在/compact或/new命令后,或在多文件工作期间上下文窗口即将满时使用此技能。
📖 中文导读:将大型任务上下文外部化到.scratch/tasks/文件中的系统,以在上下文压缩和会话重置之间保持连续性。当开始大型/复杂任务后、在/compact或/new命令后,或在多文件工作期间上下文窗口即将满时使用此技能。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: task-externalization description: System for externalizing large task context to .scratch/tasks/ files to maintain continuity across context compactions and session resets. Use this skill when starting large/complex tasks, after /compact or /new commands, or when context window is getting full during multi-file work.
Task Externalization System
Maintain continuity for large tasks across context compactions and session resets by externalizing task state to .scratch/tasks/.
When to Use
Use task externalization when:
- Starting large/complex tasks (5+ files, architectural changes)
- After
/compactor/newcommands - Context window is getting full during multi-file work
- Task spans multiple sessions
Two-File Structure
1. Overview File: .scratch/tasks.md
Tracks overall state across all tasks:
- Global Context: Shared decisions/constraints
- Current Task: Which task file is active
- Task List: All tasks with status (pending, in progress, completed)
- Cross-task Notes: Dependencies, blockers
2. Task Files: .scratch/tasks/{name}.md
Each task file contains:
- Goal: What needs to be accomplished
- Context: Background, decisions, constraints
- Files to Modify: List of files to change
- Implementation Plan: Step-by-step approach
- Progress Notes: What's done, what remains, blockers
- Testing: How to verify
See references/file-structure.md for complete examples
Quick Workflow
Starting session or after /compact//new:
- Check if
.scratch/tasks.mdexists - If yes: Read it + current task file
- Summarize and continue
Starting new large task:
- Create
.scratch/tasks/directory - Create/update overview file
- Create task file with plan
- Update overview to mark as current
- Begin implementation
During work:
- Update Progress Notes as steps complete
- Note blockers and decisions
Completing task:
- Mark complete in task file
- Update overview:
[x] - Update current task to next pending
See references/workflows.md for detailed workflows
Important Notes
- Keep progress notes current for accurate recovery
- Don't delete task files until entire effort is complete
.scratch/is already in gitignore- Task files are read/updated throughout work