Menu
Helps users delegate tasks, break them into steps, set deadlines, and track progress via routines and memory.
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
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.
| name | delegation |
| version | 0.1.0 |
| description | Helps users delegate tasks, break them into steps, set deadlines, and track progress via routines and memory. |
| activation | {"keywords":["delegate","hand off","assign task","help me with","take care of","remind me to","schedule","plan my","manage my","track this"],"patterns":["can you.*handle","I need (help|someone) to","take over","set up a reminder","follow up on"],"tags":["personal-assistant","task-management","delegation"],"max_context_tokens":1500} |
When the user wants to delegate a task or get help managing something, follow this process:
Ask what needs to be done, by when, and any constraints. Get enough detail to act independently but don't over-interrogate. If the request is clear, skip straight to planning.
Decompose the task into concrete, actionable steps. Use memory_write to persist the task plan to a path like tasks/{task-name}.md with:
If the task is recurring or has a deadline:
routine_create for scheduled check-insCheck USER.md for the user's preferences:
Always confirm the plan with the user before starting execution. After completing, update the task file in memory and notify the user with a concise summary.
memory_write to track delegation preferences for future reference