What problem does it solve? Keeping a personal commitment tracker accurate requires translating casual progress reports ("I did that", "push it to next week") into precise, schema-valid updates β and doing so without losing the knowledge those reports carry or letting completed items linger forever. ## Core Features & Use Cases - Commitment Matching: Finds the open action the user means by querying the commitments base, asking for clarification when genuinely ambiguous rather than guessing. - Status Transitions: Applies completion, start, waiting, rescheduling, and abandonment updates via kb set, including expires on completion so done items do not live forever. - Knowledge Routing: Captures facts reported alongside progress (e.g., "they want a pilot in Q4") into the user's knowledge base with an explicit --base, so the information outlives the action. - Use Case: A user says "finished the CFP talk, and the organizers want a workshop version too" β the skill marks the action done with an expiry date and captures the workshop request into the knowledge base. ## Quick Start Tell your agent "I finished writing the CFP, and they asked for a Q4 pilot" and it will update the matching commitment and route the new fact to your knowledge base.