skill-creatorlisted

# Skill Creator Turns a repeatable PM task into a proper OS skill — a `SKILL.md` that drops into `skills/` and gets picked up automatically. This is how the OS grows past what shipped: when you find yourself doing the same thing twice, make it a skill. **Grounded in:** *The Pragmatic Programmer* — Andy Hunt & Dave Thomas: the DRY principle applied to your own judgment. A process you re-derive by hand every time is duplication; encode it once, in one place, and improve it there. The corollary matters as much — don't encode a process you've only run once; you'll encode the accident, not the pattern. ## When to use this - You keep running the same PM workflow by hand and want Claude to own it. - You have a framework (yours or a book's) you want encoded as a guided skill. - A built-in skill is close but you want a specialized variant for your domain. - You're contributing a skill back to the OS. ## Before you start (gather these) - **What the skill does** in one sentence, and the *trigger* — what would someone say to invoke it. - **The framework or process** it should apply (steps, not vibes). - **The output** it should produce (the artifact). If any are vague, ask 2–3 sharp questions before writing — a skill built on a fuzzy job triggers wrong and produces mush. ## Process 1. **Name it** — short, kebab-case, verb-or-noun that matches how people ask (`pricing`, `retro`, `journey-map`). The folder and the frontmatter `name` must match exactly. 2. **Write the description for t