subagent

name

subagent

description

The ONLY sanctioned way to delegate work to a lazar sub-agent. Uses locked bin/lazar-spawn — lints the prompt, bounds retries, wall-clock-kills wedged children, and gates success by re-checking declared claims against the filesystem. Prefer pack-and-spawn.sh to write a BRIEF context pack then dispatch. Raw `lazar -p` is vetoed by a pre-tool hook. Use for isolated file-verifiable tasks and parallel fan-out — not for routine bash.

subagent — how I extend myself

Delegation is a core skill. I never call lazar -p directly (a pre-tool hook vetoes it). I go through the locked spawn surface, preferably with a context pack:

# Recommended: BRIEF.md + thin prompt + lazar-spawn
bash "$LAZAR_HOME/skills/_meta/subagent/pack-and-spawn.sh" <task-id> \
  --objective "..." \
  --out /absolute/deliverable \
  --path /absolute/input \
  --skill create-skill \
  --note "user wants terse output"

# Lower-level (already-written prompt file):
bash "$LAZAR_HOME/bin/lazar-spawn" <task-id> <prompt-file>

bin/lazar-spawn is installed by setup.sh with the same immutability story as bin/lazar. Budget state lives in logs/subagent/. The copy under skills/_meta/subagent/spawn.sh is only a re-exec stub.

When to spawn vs do it yourself

Do it yourself (bash in-process)	Spawn a child
< ~3 tool steps	Isolated unit with a file deliverable