Workflow

The final post in my series on skills for dev workflow. A /new-issue skill lets you describe a bug or feature in a sentence and get back a well-structured issue with wireframes and acceptance criteria — better than most people write by hand.

As your agent skills grow, some parts want to be their own thing. Here's how I used a simple prompt to extract a standalone /approve skill from my /next-task skill — and why thinking of skills like functions leads to better workflows.

A step-by-step guide to building a /next-task agent skill that pulls from your issue tracker, manages branches, implements changes, and opens PRs. Customize it for your own tools — Linear or Jira, GitHub or GitLab.

One of the most exciting things about LLMs is their ability to do useful things that would be hard to script in the traditional sense. Skills take this further, letting you build intelligent workflows that handle the messy, context-dependent parts of product development.

I’m actually not sure when I first noticed this. Perhaps it goes back to my teen years when I helped with the construction of our church building. Or, perhaps it was before that when I worked at a Christian camp. But there are some activites that seem to make everything else more productive. I call these sweeping activities. Sweeping activities make it easy to get work done.

As a teenager I learned to program and it wasn't long before I had a directory filled with unfinished projects. Working on a large variety of projects is a great thing when you are first learning a language or framework. It helps you begin to recocognize patterns. Patterns that end up being useful when you start going deep on larger projects.

Not quite as glamorous as The Matrix may make it appear, the command prompt is still an essential part of the modern web design workflow. Whether you’re seeking to transform your CSS with Sass, itching to try out Webpack or Typescript, or thinking about writing a program in JavaScript with Node, you’ll need to understand the command prompt.