Custom Skills: The End-to-End Workflow Made Executable

I Was Repeating Myself By the time the harness was working and I'd moved to on-the-loop development, my sessions with Claude had a rhythm. Pick up a Jira ticket. Read the requirements. Decide which part of the codebase it touches. Write failing tests. Get them approved. Implement. Run lint and tests. Commit. Open a PR. Watch CI. Review the diff. Maybe refactor. Every time, I typed the same instructions. "Here's a Jira ticket. Pull the requirements with jira issue view . Write tests first. Follow the Action pattern. Run make lint and make test before committing." It worked. But I was the ceremony. I was the one remembering the steps, enforcing the order, making sure the harness feedback loop happened. If I forgot to say "write tests first," Claude might skip straight to implementation. If I forgot to say "run lint," it might commit without checking. The workflow was good. But it lived in my head, not in the system. Skills: Slash Commands for Claude Code Claude Code supports custom skill