the-ledger

Record insights, failures, and constitutional rules in structured markdown files.

71|9|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/kucherenko/gangsta --skill the-ledger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-ledger
Source: https://github.com/kucherenko/gangsta/tree/main/skills/the-ledger
Command: npx skills add https://github.com/kucherenko/gangsta --skill the-ledger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ledger stores institutional memory across Heists—capturing successful reasoning pathways (Insights), documented failures (Fails), and governance rules (the Project Constitution) to improve consistency, learning, and governance.

Core Features & Use Cases

  • Persist Insights and Fails for audit trails and governance references.
  • Maintain a living Project Constitution that evolves with each Heist.
  • Provide quick access to historical decisions during reconnaissance and planning.

Quick Start

Create the initial docs/gangsta/constitution.md and record the first insight entry.

Frequently Asked Questions about the-ledger

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

FAQPage Schema
How do I preserve institutional memory for ongoing projects and historical failures?

To preserve institutional memory, capture insights, documented fails, and constitutional rules using a structured schema with frontmatter metadata. This ensures consistent directory layout and governance traceability across reconnaissance, planning, and execution stages.

What is a project constitution and how does it guide governance decisions?

A project constitution is a living governance document that records rules and evolves with each project. By maintaining this constitution alongside recorded fails, teams ensure historical decisions guide future governance and improve consistency.

How do I record insights and fails for project audit trails?

Record insights and fails by creating entries with enforced frontmatter metadata and a consistent directory layout. This structured approach provides quick access to historical decisions and supports audit trails and governance references.

Does capturing institutional memory require a specific directory layout or metadata format?

Yes, capturing institutional memory requires a specific directory layout and structured schema with frontmatter metadata. Enforcing this consistent format ensures traceability and governance across ongoing and historical project stages.

What's the best way to maintain a living project constitution that evolves over time?

The best way to maintain a living project constitution is to record governance rules in a structured markdown file that updates with each project. Capturing insights and fails alongside the constitution ensures it guides future decisions accurately.