Project Context Manager

Problem

WorkBuddy conversations can lose continuity across projects and sessions: restarting a project requires re-explaining background, switching projects can mix in the wrong plan, and long chats increase token cost and repeated confirmation.

How It Works

• Progressive disclosure: L1 conversation fingerprint, L2 incremental summary, L3 project template, and L4 user confirmation caches reuse approved context and process only new deltas.
• Secure cross-project access: reads are passive and explicitly authorized; cross-project content is labeled [Source: project name] and not written into the current project; sensitive data such as keys is filtered.
• Tagging: the skill suggests tags for stack, domain, and task type; user-confirmed tags support project association and tag views.
• Triggering: manual instructions, name-based activation, and optional Stop hook saving at conversation end.

Boundaries

It fits small teams or offline workspaces needing persistent project context. It does not replace repository scanning, product docs, or permission systems; cross-project use requires explicit target mention, and automatic saving needs separate configuration.