claude-tweaks:ledger

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.

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.

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.

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.

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.