qa ledger tracker

The problem

Project context resets between sessions, causing you to answer the same client or team questions repeatedly. Native chat memory fades, and managing a separate database or heavy issue tracker is overkill for simple decision logs.

What it does

• Maintains a persistent Markdown-based Q&A ledger that survives session resets.
• Updates specific rows, adds timestamps, and manages status markers directly in your project files.
• Handles table expansion and automatic file splitting when row limits are reached.
• Supports parallel answer staging and merging to prevent file corruption during concurrent edits.
• Strips bloated questions into external files to keep your primary ledger readable.

Why this beats prompting it yourself

Manual table editing with LLMs frequently breaks Markdown formatting or overwrites existing data. This skill uses a structured command set to ensure row integrity, automated pagination, and consistent status tracking that a raw prompt cannot maintain reliably.

Use cases

• Consultants managing a durable "Open Items" list for client engagements.
• Developers logging architectural decisions and their rationales in a local repo.
• Small teams tracking project-specific Q&A without external SaaS tools.
• Solo builders maintaining an append-only log of bug triage and resolutions.