dev-spawn

Topics in the source

• dev-spawn
• When to Use
• Checklist
• Phrases to commands
• Worker rules (put in every brief)
• Changing a running worker
• Rationalizations
• Red Flags

Paths: the bin/ tools and the library/ folder live in /.agents/dev-kit/; run tools by that path. Task: no DEVKITTASK set? Run /.agents/dev-kit/bin/ledger start first (it prints your id) and prefix dev-kit commands with DEVKITTASK= . below is .devkit/tasks/ at the repo root; never write run files anywhere else. Also read .devkit/memory.md if it exists. Open the host todo list (todowrite, TodoWrite or TaskCreate, whichever exists; else a checklist in /state.md) with this checklist verbatim, and tick items as steps finish. A skipped step stays listed with a reason. Run bin/ledger after every step (phase=spawn). Output would exceed about 50 lines, much reading is needed, work is independent, or you need an unbiased second pair of eyes. A long task nobody watches: also follow library/deep/overnight. Not for small edits, or a step whose result you need in context to decide the next one. You own: delegated work and the decision to accept or reject each handoff. Reads: always library/principles (step 0), library/state. For a long task nobody watches: library/deep/overnight. [ ] 0. Skim library/principles (about 700 tokens); open a deep file only when its trigger matches. [ ] 1. Pick the sh

This is an excerpt. Refer to the complete source and its current requirements.