What problem does it solve? In long design or planning chats, open questions, pending decisions, and unresolved suggestions drown in the message flow. This Skill makes tracking explicit: every problem, issue, and suggestion gets a numbered entity with a defined status, and every agent message ends with a roll of what is still open. ## Core Features & Use Cases - Explicit state machines: Problems (P) move through open, clarified, delivered, or canceled; Issues (I) open and close; Suggestions (S) are confirmed or declined — all with strict transition rules. - Ambiguity safety: Soft or ambiguous user replies ("probably", homonyms, partial answers) become issues instead of self-served confirmations, preventing silent misinterpretation. - Mandatory Open Items block: Every message ends with a compact list of active entities, or a short blessing phrase when nothing is open. - Use Case: During a multi-hour architecture discussion, the user activates the skill so that every open design question is numbered (P1, I1_02, S1_01), scope expansions are flagged with a renamed! marker, and nothing agreed or pending is ever lost. ## Quick Start Tell the assistant to activate problem tracking mode for this conversation so every open question and decision is explicitly numbered and tracked.
