Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Coding
foreman
Try itDispatch-and-acceptance control desk for farming coding work out to background agents. Probes which worker backend is actually usable, gives each task its own git worktree, sends it to a worker agent via the handoff CLI, takes delivery only as a real commit inside a path whitelist, then gates the merge behind an acceptance protocol whose core rule is that the builder may never touch the tests, assertions, or CI config that judge it. Be aware before using it — it sends repository content to the worker backends you configure; its probes read your local agent login status and may make one minimal request to a backend; and the optional caged worker starts a Docker container, passes DEEPSEEK_API_KEY into it, and lets the worker skip permission prompts inside that container. Use it when batching implementation work out to background agents, or when accepting code that someone else — human or agent — built.
What it does
Entry decision (settle this first, then read the matching chapter)
The skill document
foreman — thin router
Entry decision (settle this first, then read the matching chapter)
- Default (there is work to farm out): read
dispatch.mdin this directory and run the dispatch chapter. Once every delivery has passed intake, automatically readverify.mdand enter the acceptance chapter — do not wait to be asked again. - User says "just dispatch, skip acceptance for now": run
dispatch.mdonly and stop at intake. /foreman verify, or acceptance only (including code somebody else handed you): readverify.mddirectly.
Global invariants (both chapters, ahead of any playbook)
- State goes to disk. Always under
.foreman/— one.jsonper task, onebatch.jsonper batch. First action on every entry into foreman: scan.foreman/for overdue and unsettled tasks and reconcile them before starting anything new. - One shared escalation budget. The same
error_fingerprintshowing up a second time → escalate immediately. Dispatch reworks plus acceptance repairs reaching 4 rounds combined → circuit-break and report to the user. - The measuring instruments are protected. If a builder's diff touches tests, assertions, or CI config → reject the delivery. No exceptions. This is the only mechanism in the entire scheme that prevents a consistent false green: a builder that can edit the ruler can always make the work measure up.
- Judge on data, not exit codes. Acceptance tooling routinely exits 0 no matter what it found. Read only the manifest/findings that this run newly generated.
- The main session only judges and merges. Executable work gets farmed out — keep the expensive model's budget for decisions.
Related skills
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Read and write Excel workbooks, worksheets, ranges, tables, and charts in OneDrive through Microsoft Graph with managed OAuth.
More from xiaoba-dev
Browse all skillsRoute any Rotifer request to the right sub-capability — onboarding, scaffolding, diagnostics, search, or fidelity upgrade.
Build a Rotifer Agent from existing Genes through a 7-phase workflow of decomposition, composition, creation, and testing.
Compare two Rotifer Genes head-to-head and get a Markdown report with F(g) fitness and V(g) security grades.
Rank an Agent's Rotifer Genes against the Arena and swap in stronger ones. Invoked explicitly via /evolve — scan local capabilities, compare Genes, inspect fitness scores, and replace weak ones with user approval. Not for capabilities outside Rotifer.
Cross-vendor adversarial review. WARNING — this sends your brief, and any source files you approve, to a model hosted by a THIRD-PARTY vendor, where it stays in that vendor's session history under their retention terms. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; every objection carries a verifiable anchor; the defender rules with an evidence tag on each ruling; the final round classifies into still-disputed / unresolved / verified-consensus instead of forcing agreement; a fresh-session judge is mandatory whenever the outcome looks too clean. Invoke only when the user explicitly asks for an adversarial review by a model from another vendor. One model role-playing several experts is not this skill.
Session knowledge distillation: assign what you just learned in this session into an agent's four-layer persistent knowledge base (rule / memory / skill / decision record). The core is four disciplines — search before adding, pick the right layer, guard against bloat, and run a hygiene pass before landing anything. Fits agent workflows that already have (or want to build) these four layers; this is not a general note- taking tool. Invoke explicitly at the end of a session to consolidate what was learned.