context-capsules

Track project decisions, questions, and progress in a local .capsule directory.

12|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/CognitivTrust/context-capsules --skill context-capsules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-capsules
Source: https://github.com/CognitivTrust/context-capsules/tree/main
Command: npx skills add https://github.com/CognitivTrust/context-capsules --skill context-capsules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires portalocker==2.10.1, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a way to store and access the reasoning behind code decisions, making it easier to understand and maintain projects over time.

Core Features & Use Cases

  • Decision Tracking: Record and store decisions made during the development process.
  • Progress Logging: Keep track of completed tasks and progress.
  • Question & Resolution: Document open questions and their resolutions.
  • Task Lifecycle: Track the lifecycle of tasks, including start and end events.
  • Evidence Verification: Ensure the existence of cited evidence (files, commits, etc.) locally.
  • Tool-Agnostic: Can be used with various tools and AI agents.
  • Use Case: Imagine you are working on a complex project with multiple contributors. Use this Skill to document the reasoning behind each decision, ensuring that everyone on the team has the context they need to understand and contribute to the project.

Quick Start

Initialize a new capsule by running 'capsule init'. Load the capsule by running 'capsule load'. Record a decision by running 'capsule record decision --decision "Use OAuth2 authorization-code flow" --rationale "server-side secret; no token in the browser" --evidence file:auth/google.py --by cursor'.

Frequently Asked Questions about context-capsules

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

FAQPage Schema
How do I track decisions and project reasoning locally during software development?

Project memory tracking stores your development intent, decisions, and task progress locally in a `.capsule/` directory. You interact with this memory using the `capsule` CLI to record rationale and link evidence.

What is the best way to document open questions and their resolutions in a codebase?

Documenting open questions and resolutions involves logging them as structured events via the `capsule` CLI. This captures the context locally, ensuring team members and tools can access the reasoning behind code changes.

Does this local-first decision tracking tool work with AI agents and collaborative development environments?

Yes, the tool-agnostic design supports collaborative development and AI agents. It stores data locally in a `.capsule/` directory, allowing various tools and team members to access the shared project context.

How do I verify cited evidence like files and commits when logging task progress?

Verifying cited evidence involves checking the local existence of files and commits referenced during progress logging. The system ensures cited evidence exists locally when you record decisions and task lifecycle events.

Do I need Python 3.11 to use the capsule CLI for project memory management?

Yes, Python 3.11+ is required to run the `capsule` CLI for project memory management. The local-first tracking system depends on this runtime environment to store data in the `.capsule/` directory.

Why should I use a local-first project memory system instead of general note-taking for software decisions?

A local-first project memory system provides structured task lifecycle tracking and evidence verification directly within your codebase. Unlike general notes, it durably links decisions and rationale to local files and commits for precise team context.