Menu
Summarize completed repo-worker changes with test and risk status.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Run and inspect SWE-bench benchmark workflows for alan's coding line. Use this when: - The user wants to run SWE-bench Lite or curated SWE-bench subsets - The user wants to prepare benchmark workspaces or materialize suite manifests - The user wants to score benchmark predictions with the official harness - The user wants benchmark operations to remain separate from the repo-coding product contract
Execute repo-local code edits and run deterministic verification.
Delegate bounded repo-scoped coding work to a fresh repo worker. Use this when: - alan has already selected the target repo or directory - The task needs inspect -> plan -> edit -> verify -> deliver inside that bound scope - The work should run in a focused child runtime instead of the parent steward
Manage persistent Memory Store files across Agent Processes. Use this when: - Continuing work started by an earlier Agent Process - The user references prior decisions, constraints, or history - Stable, user-confirmed information should be retained - Durable handoff or topic notes need inspection or maintenance
Inspect and operate the native alan shell control surface. Use this when: - The user asks about spaces, tabs, surfaces, panes, focus, or splits - alan needs to decide which pane or surface should receive an action - alan needs to create a space, split a pane, focus a pane, or send text - The task depends on understanding the outer terminal app rather than only understanding Alan Process state This skill assumes the local `alan shell` CLI namespace backed by the shell's IPC/socket API. If that CLI is unavailable, report that clearly and fall back to other available context.
Create and manage structured execution plans for complex multi-step tasks. Use this when: - Task requires more than 3 distinct steps - Work is expected to span multiple context windows - There are logical dependencies between steps - You need to track incremental progress - User asks for something complex that benefits from a plan Do NOT use for simple single-step tasks or quick questions.
| name | repo-worker-deliver |
| description | Summarize completed repo-worker changes with test and risk status. |
| metadata | {"short-description":"Produce repo-worker delivery summaries with evidence","tags":["coding","delivery","repo-worker","handoff"]} |
references/delivery_contract.md so the parent steward can ingest the
bounded delivery artifact directly.Changed: or append extra commentary outside the
JSON payload.