Skills

For the past couple of weeks I’ve been running a scrum-for-one framework on a real project. Enough sessions in to see the payoff: tighter planning, tracked velocity, and a self-learning loop that stops me from repeating the same mistakes. But the MVP was an MVP, with its limitations and trade-offs: skills updated their own SKILL.md files in place, artifacts were shared across every project, and so on. So I decided to push it further. I wanted hands-on experience building a non-trivial plugin, and a chance to fix those limitations. The result, booping, is now published as a Claude Code plugin (alpha). ...

Can the right methodology consistently produce production-quality code from an AI coding agent? Well-decomposed architecture. Maintainable code that can be refactored without disproportionate rewrites. Clean abstractions that survive the next feature. It started with one planning skill. I was tired of Claude Code implementing features freestyle, producing code that worked but couldn’t be extended. So I wrote a /grooming skill that reads the codebase and produces a structured plan before any code is written. That helped. Then I added agent delegation to avoid context rot on long sessions. Then story points for tracking throughput. Then retrospectives and lessons to stop repeating the same mistakes across sprints. Four skills, a ~/Claude/ knowledge base, and a self-learning loop that makes the agent genuinely improve across sessions. ...