Menu
Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commitment-digest |
| version | 0.2.0 |
| description | Compose and deliver summaries of open commitments, deadlines, pending signals, and resolution suggestions. |
| activation | {"keywords":["show commitments","commitment digest","commitment summary","commitment report","open commitments","my obligations","what do I owe","pending tasks","what's overdue","what's due","commitment status"],"patterns":["(?i)(show|list|summarize|review) (my )?(commitments|obligations|deadlines|tasks)","(?i)what('s| is| are) (pending|overdue|due|open)","(?i)commitment (digest|report|status|summary)"],"tags":["commitments","digest","reporting"],"max_context_tokens":1500} |
Compose a summary of the user's current commitments. Used both in-conversation (user asks "show commitments") and by the commitment-digest mission for scheduled delivery.
memory_tree("projects/commitments/open/", depth=1) — list all open commitment files (skip README.md)memory_read each file to extract frontmatter: status, urgency, due, delegated_to, resolution_path, stale_after, tagsmemory_tree("projects/commitments/signals/pending/", depth=1) — count pending signals (skip README.md)memory_tree("projects/commitments/resolved/", depth=1) — count recently resolvedUse memory_tree and memory_read for digest assembly. Do not use CodeAct,
shell commands, or creative-generation tools to count or summarize
commitments.
Group commitments and present in this order:
## Commitments — <today's date>
### Overdue / Critical
- **<title>** (due <date>) — owner: <owner>
→ <resolution suggestion based on resolution_path>
### Due This Week
- **<title>** (due <date>) — owner: <owner>, delegated to: <person>
### Waiting / Delegated
- **<title>** — waiting on <person> since <date>
→ (follow-up suggested) if not updated in 3+ days
### Open (no deadline)
- **<title>** — owner: <owner>
### Agent Can Handle
- **<title>** — I can <suggested approach>. Want me to proceed?
### Pending Signals (<count>)
<count> unprocessed signals. Say "review signals" to triage them.
### Recently Resolved
- <title> (resolved <date>)
---
Did I miss anything? Tell me if I overlooked an obligation.
Rules:
stale_after as "(stale — still relevant?)"resolution_path: agent_can_handle, describe what the agent would do and ask for approvalresolution_path: needs_reply, offer to draft a response if possiblemessage tool to the user's preferred channelUse when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Navigate building a user-facing feature in the Reborn stack (a capability that crosses product_workflow → composition → webui_v2 → runtime/serve → frontend). Use when planning or implementing any new Reborn settings page, endpoint, facade method, or runtime-backed capability — especially before writing code, to avoid rebuilding what already exists and to wire it in one pass instead of layer-by-layer.
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Generate or update the IronClaw architecture overview video using Remotion. Use when asked to update, regenerate, or modify the architecture video, add/remove scenes, or reflect codebase changes in the video.
Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_reborn_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.
Use when starting work in the IronClaw repo, deciding where a feature/fix/prompt/doc belongs, tracing how a request flows, looking up which crate owns a subsystem, or when repo docs, the knowledge graph, or component names seem stale, missing, or contradictory.