claude-tweaks:ledger

Track and resolve open items in a markdown ledger across pipeline phases.

2|Updated Feb 20, 2026

Search Tags:#workflow #documentation #build #review #gate #ledger #open-items

Ready to run

npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-ledger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-tweaks:ledger
Source: https://github.com/thomasholknielsen/claude-tweaks/tree/main/skills/ledger
Command: npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-ledger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the open items ledger that tracks findings, operational tasks, and observations across pipeline phases. The ledger is a markdown file that carries state between skills and survives context window compression.

Core Features & Use Cases

Tracks open items, decisions, and actions across /claude-tweaks build/test/review/wrap-up flows.
Standalone: inspect the current ledger and trigger the nothing-left-behind gate when items remain unresolved.
Integrates with docs/plans/YYYY-MM-DD-{feature}-ledger.md to record open items and resolutions for a given pipeline run.

Quick Start

Create a new ledger file at docs/plans/YYYY-MM-DD-{feature}-ledger.md and begin logging open items.

Frequently Asked Questions about claude-tweaks:ledger

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

FAQPage Schema

How do I track open items and unresolved findings across a build and review pipeline?▼

You track open items across a build and review pipeline by maintaining a markdown ledger file that captures findings and operational tasks. This ledger carries state between pipeline phases and survives context window compression.

What is a nothing-left-behind gate in a development workflow?▼

A nothing-left-behind gate is a workflow enforcement check that ensures all open items in the ledger are resolved before wrap-up. It triggers when items remain unresolved, preventing findings from being missed across pipeline phases.

How do I record open items and decisions in a markdown ledger during test and review phases?▼

You record open items and decisions in a markdown ledger by appending findings, updating statuses, and logging resolutions during test and review phases. Create a ledger file at docs/plans/YYYY-MM-DD-{feature}-ledger.md to start logging.

Can I use a markdown ledger to manage pipeline state when context window compression occurs?▼

Yes, you can use a markdown ledger to manage pipeline state because it survives context window compression. The ledger file carries state between skills and maintains open items, decisions, and actions across build, test, review, and wrap-up flows.

What is the best way to organize unresolved tasks and observations across software engineering phases?▼

The best way to organize unresolved tasks across engineering phases is using a markdown ledger that tracks findings, operational tasks, and observations. It enforces the ledger workflow by appending items and updating statuses throughout the pipeline.