One repeatable RSI pass over CODE SLOP — the slop the compiler can't see. Runs the code-slop scorecard (tools/codeslopscorecard.py), reads the slop-debt work-list, retires debt worst-first using ONLY genuine fixes...
One repeatable pass that stops fak from re-inventing known kernel art - before writing or optimizing a compute kernel (a quantized GEMM, a fused attention, a KV-cache reuse, a MoE dispatch, a Metal/CUDA kernel), it...
Apply the two new-work defaults — ship the minimal WORKING end-to-end spine first (or file the spine as its own issue), then fan out the 3..50+ follow-on QA/dogfood/productization backlog at creation time via fak...
One repeatable pass that keeps fak trustworthy while it iterates fast — the question no other scorecard asks: as we add items quickly, how do we KNOW a regression / tail-wag / confusion landed, and how do we REVERT...
Turn a fak stale-work packet into dedicated, contract-valid issue units, collision-safe dispatch waves, and witness-only reconciliation. PLAN by default; use when an operator asks to adjudicate stale-work...
The operator loop over the steer-prs overlay (fak steer prs) — fak's read-only view that folds the pending dev->release trunk delta into PR-sized units per (fak ) ship-stamp and renders them...
One repeatable pass that keeps fak as STEERABLE as it grows — the one scorecard whose every KPI is growth-invariant, so a 2x-larger repo with the same discipline scores the same. Runs the steerability scorecard...
Inventory and deeply study innovation in upstream pull-request queues, including open and unmerged PRs, then turn selected mechanisms into provenance-honest fak research and deduplicated GitHub issue drafts. Use for...
High-priority deep study of external code and proposals for fak. Invoke proactively whenever a repository, package, PR, issue, release, paper-with-code, or implementation is relevant—not only on explicit study...
Plan, price, launch, monitor, and reconcile bulk headless issue-resolution work safely. Use when an operator asks for a super loop, worker wave, detached issue workers, backlog draining, capacity/status,...
Find the most "tail wagging the dog" part of the system — a peripheral or secondary concern that is disproportionately driving core design decisions. Produces a ranked list of inverted-priority findings with...
One repeatable pass that decides whether a GitHub ticket is a single dispatchable unit of agent work — or names exactly which of the six scope axes it fails and how to fix it. Wraps the native scope toolkit (fak...
Runs on the StopFailure event for overloaded, server_error and rate_limit tool calls, executing rate_limit_rewake.py via python with --workspace. From anthony-chaudhary/dos-kernel.
Adjudicate a GitHub issue's "this is resolved" claim from witnesses the claimant didn't author — then close it carrying the evidence, or refuse with the typed gap. Use when an issue looks already-solved, after landing a fix that should have closed one, or to sweep open issues for silently-resolved ones.
Pick the next most important open GitHub issue this agent can actually complete, make its done-condition true, land it with witnesses (suite + parity + commit-audit), and priority-tag every issue touched along the way. Use when asked to "work the backlog", "complete the next most important issue", or to fix a specific…
Cut a versioned release of the DOS kernel — bump the version, draft release notes, commit, tag, push to master, and create a GitHub release. The tag push triggers the gated PyPI publish pipeline (publish.yml); the skill surfaces the run and its approval gate.
Promote an already-shipped rolling release (vX.Y.Z) of the DOS kernel to a named stable channel — gated on a green kernel suite + a green third-party CI run on the candidate + a clean truth syscall + a soak window. Writes an evidence file and adds a stable/ git tag on the same commit. Does NOT bump versions or build…
Instructions for anthony-chaudhary/dos-kernel, covering what dos is (the 30-second version), run it yourself first — the 60-second proof, when the user asks you about dos (the consumer moves), build, test, and check your work and the layout in one screen.
Instructions for anthony-chaudhary/dos-kernel, covering dos — the dispatch operating system, the layering — keep these apart, the syscall abi, install & test and dos on dos — dogfood the kernel here.