automate-melisted

# Automate me A guided flow for turning the user's working conventions into a skill agents will follow. The output is one `-mode` skill tailored to them (e.g. `jay-mode`, `priya-mode`). This skill sequences an inline mining pass (see step 1), the bundled [authoring playbook](../meta-mode/playbooks/authoring-a-skill.md), and the **unslop** skill. If a selected-skills installation omits either sibling, use step 4's standalone draft rules and check the prose directly. ## Flow ### 0. Check for an existing skill Look recursively for the active Harness's project and user skill roots for `*-mode/SKILL.md` matching the user's handle. Mode skills can live in a personal category directory, not only at the top level. If one exists, confirm intent with `ask the user` (unless they already said "update my skill" or similar): - Update the existing skill (default for repeat runs) - Start fresh (rare, ask why before doing it) Update mode changes the rest of the flow: - Step 1 mines only history since the skill was last edited (`git log -1 --format=%cI <path>`). - Step 2 asks what's changed or missing, not what to capture from zero. - Step 4 edits the existing file in place. Preserve sections the user hasn't contradicted. Revise ones with new evidence. Add new sections only for genuinely new rules. ### 1. Mine their history Locate the active workspace's transcripts before fanning out. Use [recall's history reader](../recall/references/history-sources.md) to list scoped session IDs and