Save Work Context

Capture work context into timestamped markdown logs at .agents/workctx/.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Event-Based-Banking-Application/arya-banking --skill save-work-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Save Work Context
Source: https://github.com/Event-Based-Banking-Application/arya-banking/tree/main/.agents/skills/save-workctx
Command: npx skills add https://github.com/Event-Based-Banking-Application/arya-banking --skill save-work-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures the agent's work context (accomplishments, problem statements, fixes, and approaches) into a markdown log stored at .agents/workctx/ so knowledge is retained across sessions.

Core Features & Use Cases

  • Automatic capture of accomplishments, decisions, and fixes at the end of tasks.
  • Timestamped, standardized markdown entries for easy retrieval and auditing.
  • Manual trigger via user prompts such as "wrap up", "log this", or "save progress" to create a work-context entry.

Quick Start

Invoke this skill at the end of a feature or debugging session to save a timestamped work-context entry into .agents/workctx/.

Frequently Asked Questions about Save Work Context

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

FAQPage Schema
How do I automatically save AI agent work context and debugging history to a markdown log?

You can automatically save AI agent work context by triggering a skill that captures accomplishments, problem statements, and fixes into a centralized markdown log. This ensures your knowledge management and worklog history remain traceable across sessions.

What is the best way to retain AI agent accomplishments and fixes across different work sessions?

Retaining AI agent accomplishments requires persisting work context into a centralized markdown log. By writing timestamped, standardized entries into a specific directory, you create a traceable history of decisions and problem statements for future retrieval.

How do I log feature completion and code push decisions for future debugging reference?

To log feature completion and code push decisions, you can invoke a context-saving mechanism at the end of a task. It applies a standardized template to document your approaches and fixes, creating a timestamped markdown entry for auditing.

Can I manually trigger a worklog entry to save progress during a debugging session?

Yes, you can manually trigger a worklog entry by using prompts like "wrap up", "log this", or "save progress". This creates a standardized work-context markdown entry to preserve your current debugging session and decisions.

Does saving work context require any specific dependencies or environment setup?

Saving work context requires no external dependencies. It operates independently to write timestamped markdown files into a designated directory, ensuring your worklog and knowledge management process remains self-contained.

When should I avoid using automated work context logs for my AI agent?

You should avoid using automated work context logs for trivial tasks that do not involve significant accomplishments or complex problem statements. It is designed for feature completion and debugging sessions where traceable history adds clear value.