capture-skill

Capture a practice the user is introducing as one new skill, after testing that none of the skills they name already own it. Use when the user says they have skills for some jobs but something is missing, says a practice is not captured or is not covered, says nothing captures this, or introduces a workflow that should become a skill — including "we have skills for X, Y, and Z, but I'm missing something." Read the named skills first. If one owns the practice, name it and stop. If the gap is only a missing handoff sentence, patch that boundary and stop. Otherwise confirm the shape, write one skill whose description and steps send each neighboring job to its own skill, and add the return pointer on each neighbor. Do not use to record session friction into whatever instruction home fits (compound), to revise a skill the user already named, or to carry out the practice after the skill exists.