Index of every page on this site: llms.txt
All skills
scode avatar

/scode-agent-delegation

@03a9f7f
Run it yourself

How to work with a delegate once a caller has decided to use one: the self-contained task spec, the artifact-file rule, the no-VCS rule, the run id and run directory, the two-stop checkpoint protocol for delegates that write code, crash and resume handling, and the gate that judges the result and returns one of a fixed set of verdicts. Loaded by orchestration skills at the moment they delegate; inert on its own, never active for a session, and not meant to be invoked by the user directly.

  • 8 files
  • 72.8 KB
  • Updated 2 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/scode/dotfiles/scode-agent-delegation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

integrating.md

≈436 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Integrating isolated writers

Read this file when the caller has an accepted result from a writer that worked in an isolated tree. The caller decides when writers may run concurrently and in isolated trees, and owns the merge; this is how that merge is done without losing work. The inputs are the caller's: which trees are isolated, the recorded base each started from, and the gate verdict for each result.

  • Integrate serially: extract each delegate's complete change set (plain git diff misses untracked files — new files, renames, and mode changes all count), and apply it to the main tree one at a time, re-running the relevant checks after each apply. Keep each isolated tree until its result has been applied and validated. A result the gate returned as substantive failure, structural is discarded along with its tree, which is cheaper than untangling it from a shared one.
  • Conflicts between accepted results are the caller's to resolve and an expected cost of this mode — disjoint task scopes make them rare, not impossible. Textual conflicts surface at apply time, but semantic conflicts apply cleanly, and a delegate's own checks only ever validated its isolated baseline. Re-run the relevant checks on the integrated main tree after each apply, and again after the last one.
  • A delegate's changes are attributable only against a recorded baseline. For a shared tree that is the git status / git diff taken before launching; for an isolated tree it is the clean base the caller created it from. When a writer is killed or its result rejected, the caller removes its attributable changes (or discards its tree) before relaunching anything in that tree, so the retry starts from a known state.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 03a9f7f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago

README badge

README badge for scode/dotfiles/scode-agent-delegation