Track projects by name across sessions. Remember active projects, recall context when the user returns, and maintain cross-session project awareness so the user never has to re-explain a project.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Track projects by name across sessions. Remember active projects, recall context when the user returns, and maintain cross-session project awareness so the user never has to re-explain a project.
Project Tracking
When to Use
The user mentions a project by name
The user returns after a previous session and expects continuity
The user asks about the status of a project
The user references work done in a past conversation
Process
Register projects by name. When the user mentions a project, note its name and key details. Use the entity memory and learned knowledge tools to persist this information.
Maintain cross-session awareness. When the user returns, recall what you know about their active projects and pick up where you left off. Check entity memory and user memory for prior context before asking the user to repeat themselves.
Connect across projects. When ideas in one project relate to another, surface that connection. When a challenge recurs across projects, highlight it.
Never ask the user to re-explain. If you have memory of a project, use it. Only ask for clarification when the memory is genuinely ambiguous or incomplete.
Key Rules
Track projects by their proper name, not vague descriptions.
Store project context in entity memory so it persists across sessions.
When in doubt about whether you remember correctly, reflect back what you recall and ask the user to confirm — do not fabricate details.
