Menu
Track delegated commitments, set follow-up timers, and generate nudge reminders when updates are overdue.
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 | delegation-tracker |
| version | 0.1.0 |
| description | Track delegated commitments, set follow-up timers, and generate nudge reminders when updates are overdue. |
| activation | {"keywords":["delegated","assigned to","waiting on","follow up with","check with","ask them","handed off","they said","blocked on","no response","nudge","chase up"],"patterns":["(?i)(delegated|assigned|handed off) (to|this to)","(?i)(waiting|blocked) on .+ (to|for)","(?i)follow up with .+ (about|on|regarding)","(?i)check (with|in with) .+ (about|on)","(?i)(tell|ask) .+ to .+"],"tags":["commitments","delegation"],"max_context_tokens":1200} |
Track commitments that depend on someone else. The triage routine will flag stale delegations for follow-up.
User says: "I asked Sarah to handle the deployment" or "tell ops to investigate staging" or "waiting on legal for the contract review."
This skill is only successful if the delegation is persisted in workspace memory. Do not just acknowledge or summarize a delegation.
Execution order is mandatory:
projects/commitments/open/Never say "tracked", "saved", or "I'll flag it" unless the corresponding
memory_write succeeded.
Action:
projects/commitments/open/ via memory_searchdelegated_to: <person/team>, status: waitingprojects/commitments/open/ with:---
type: commitment
status: waiting
urgency: <infer from context>
due: <if mentioned, else null>
created_at: <today>
owner: user
delegated_to: <person or team name>
source_signal: null
tags: [delegation]
---
# <What was delegated>
<Description of what was delegated and to whom.>
## Follow-up
- Delegated on: <today>
- Expected response by: <date if given, else 3 days from now>
- Last checked: never
User says: "Sarah got back to me about the deployment" or "legal approved the contract."
Action:
memory_search or memory_tree("projects/commitments/open/")projects/commitments/resolved/open or waitingThe triage routine handles automated follow-up detection. It reads open commitments where delegated_to is set and status: waiting, checks the "Expected response by" date, and flags overdue items in the triage alert.
When the user asks to follow up explicitly ("nudge Sarah about the deployment"), draft a brief follow-up message and offer to send it if a channel to that person is available.
Use 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.