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 orchestrates three passes: an inline mining pass (see step 1), skill authoring (the host's skill-authoring skill when installed, otherwise direct SKILL.md writing), and the **unslop** skill (prose discipline). It sequences them; it doesn't replace them. ## Flow ### 0. Check for an existing skill Look recursively for `.claude/skills/**/*-mode/SKILL.md` and `~/.claude/skills/*-mode/SKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.claude/skills/<handle>/`), not only at the top level. If one exists, confirm intent with `AskUserQuestion` (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 (Claude Code: `~/.claude/projects/<slug>/`, slug = workspace path with each "/" turned