Power-User Patterns
Power-User Patterns
From One-Off Workflow to Permanent Plugin
Once a workflow runs three times, it's worth packaging.
You wrote a release-notes workflow three months ago. It pulls from your issue tracker, groups the changes, drafts a summary in your team's tone. It lives loose in your .claude/ setup as a skill and a couple of standing instructions, and it works. You run it every Friday without thinking about it.
This week a colleague watched you run it and asked for a copy. So you pasted the instructions into Slack. They tweaked a line, skipped a step, pointed it at the wrong project. Now there are two versions: yours, and a worse fork drifting in someone else's chat. Next month a third person asks, and you do the whole thing again.
The workflow was never the problem. You built something durable and kept treating it as disposable, re-pasting it instead of packaging it.
A workflow you've run enough times to trust is no longer an experiment. It's an asset. And assets get packaged, versioned, and handed out as one thing.