Builder Methods library
Modular agent skills
The skill writes one kind of proposal well; now we restructure it into a library of interchangeable sections, step files, and a shared training folder.
Part B of the first example. Real proposals are assembled from parts: different scope sections, pricing options, and structures per client. We restructure the skill through bm-skill-builder: mine the past proposals into a library of section modules with a note on when each applies, add selection logic driven by the client's situation and your interview answers, and set one hard rule: the skill only assembles from approved modules and names any gap instead of inventing a section. Along the way SKILL.md gets unpacked into step files, a positioning doc lands in a repo-level training folder, and we walk the new tree to see why it's shaped that way.
What's covered:
- When a simple skill has earned more structure
- Mining past work into a module library
- Selection logic: picking modules from the client situation and interview answers
- The closed-library rule and why predictable proposals matter
- Unpacking SKILL.md into a steps folder
- Why training material lives at the repo root, outside the skill