dev-learn

Topics in the source

• dev-learn
• When to Use
• Checklist
• Rationalizations
• Red Flags
• Verification

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. 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=learn). The dev-kit repo is the live library, so nothing is edited there until the user approves. bin/learn count is above 0 (reconcile says "learnings queued"), a task just closed, or the user says "learn from this". Not for project-specific facts: those stay in .devkit/memory.md. You own: library edits drafted from queued learnings; nothing merges without the user's approval. Reads: always library/principles (step 0), library/state. To classify a lesson: library/recipes/index and library/deep/encode-lessons. [ ] 1. List: /.agents/dev-kit/bin/learn list. Nothing queued: stop and say so. [ ] 2. Dedupe: search the library (prin

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