Can this skill be used for simple one-off tasks?

While possible, it is specifically optimized for complex, multi-step tasks. Simple questions or single-file edits can usually be handled without the overhead of the full planning framework.

What is the 'working memory on disk' concept?

It is a strategy that treats the filesystem as persistent RAM, storing goals and discoveries in markdown files so they aren't lost when the AI's context window reaches its limit.

What is the benefit of using session hashes in code comments?

Using hashes creates a stable backlink between a specific line of code and the documentation that explains the reasoning, errors, and research behind that change.

How does the 2-Action Rule improve AI performance?

By forcing the AI to write down findings after every two information-gathering steps, it prevents vital data from being forgotten or overlooked during long, complex sessions.

Where are the planning files stored in my project?

Planning files are stored under docs/en/developer/plans/ / to ensure they are version-controlled, durable, and easily linkable from your source code.

Persistent Task Planning & Traceability

Name: Persistent Task Planning & Traceability
Author: hookvibe

byhookvibe

Productivity & Workflow

Implements a file-based working memory system for persistent task tracking and full traceability within complex development workflows.

About

This skill enables a 'working memory on disk' approach by offloading Claude's planning and research to the local filesystem. By maintaining structured markdown files—including task plans, findings, and progress logs—within hashed session folders, it ensures that complex, multi-step tasks remain organized, durable, and fully traceable. This methodology prevents goal drift, preserves multimodal information that might otherwise be lost from the context window, and creates a permanent audit trail from code comments back to the original strategic reasoning.

Key Features

Durable Session Folders: Creates unique hashed directories for every complex task to store persistent planning assets.
3-Strike Error Protocol: Enforces a systematic debugging workflow that moves from targeted fixes to alternative methods after repeated failures.
Code-to-Plan Traceability: Implements a standardized hashing system for linking inline code comments directly to plan documentation.
Triple-File Architecture: Utilizes specialized templates for task plans, research findings, and session progress logs.
0 GitHub stars
The 2-Action Rule: Ensures key discoveries are saved to disk after every two information-gathering steps to prevent context loss.

Use Cases

Conducting deep-dive technical research where findings must be preserved for future development phases.
Managing multi-phase refactoring projects that span dozens of file changes and require persistent context.
Maintaining a clear audit trail for compliance or code review by linking commits to structured plan files.

About

Key Features

Durable Session Folders: Creates unique hashed directories for every complex task to store persistent planning assets.
3-Strike Error Protocol: Enforces a systematic debugging workflow that moves from targeted fixes to alternative methods after repeated failures.
Code-to-Plan Traceability: Implements a standardized hashing system for linking inline code comments directly to plan documentation.
Triple-File Architecture: Utilizes specialized templates for task plans, research findings, and session progress logs.
0 GitHub stars
The 2-Action Rule: Ensures key discoveries are saved to disk after every two information-gathering steps to prevent context loss.

Use Cases

Conducting deep-dive technical research where findings must be preserved for future development phases.
Managing multi-phase refactoring projects that span dozens of file changes and require persistent context.
Maintaining a clear audit trail for compliance or code review by linking commits to structured plan files.