context

Locates and summarizes project progress from a persisted progress.txt file.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sujithatzackriya/skills --skill context-sujithatzackriya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context
Source: https://github.com/sujithatzackriya/skills/tree/main/skills/context
Command: npx skills add https://github.com/sujithatzackriya/skills --skill context-sujithatzackriya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted cycles by loading the project’s persisted session bible (progress.txt) so you start with the same goals, TODOs, and known issues the team already captured.

Core Features & Use Cases

  • Loads session context from progress.txt by locating it across the Claude memory directory, docs, root, tasks, or by searching the repo when needed.
  • Summarizes progress and constraints (project identity, completed work, next actions, and known issues) without dumping the entire file.
  • Forces an explicit next step by asking what you want to work on today, avoiding accidental work injection or skipping prioritization.

Example use case: You return to a repo after a break and remember there were open TODOs and constraints, but not the details—run context loading to re-sync and then choose the next TODO to tackle.

Quick Start

Ask the assistant to load project context by saying: /context.

Frequently Asked Questions about context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a project and load previous session context in Claude?

To resume a project, load previous session context by locating a progress.txt file across memory directories, docs, or the repo root. The Skill summarizes project identity, completed work, and known issues in 10-15 lines, then prompts you to choose the next task.

What is the best way to track project progress and TODOs across coding sessions?

Track project progress and TODOs by maintaining a session bible file. The Skill reads this persisted file to synchronize your starting point, summarizing current status and constraints so you avoid guessing what remains to be done.

How do I find a progress tracking file if I forgot where it is saved in my repository?

Find a progress tracking file by searching candidate locations like Claude memory, docs, repo root, and tasks directories. If the file is not found there, the Skill performs a repo-wide search, confirms the found path with you, and summarizes the contents.

Can I use this context loading approach to explore an unfamiliar codebase?

Yes, you can use context loading to explore an unfamiliar codebase. The Skill locates the project's session bible, summarizes the project identity and known issues, and asks what you want to work on today without automatically starting implementation.

Does loading project context automatically start working on open TODOs?

No, loading project context does not automatically start working on open TODOs. The Skill forces an explicit next step by asking what you want to work on today, preventing accidental work injection and ensuring you prioritize tasks.

Why should I use a session bible for workflow resumption instead of relying on memory?

Use a session bible for workflow resumption to prevent wasted cycles and avoid guesswork. The Skill loads persisted goals, TODOs, and known issues from progress.txt, providing a synchronized starting point so you immediately recall project constraints.