workflow · brianlovin — Claude Code skill: plan, verify, fix autonomously

What workflow does

The skill lays out six rules. For anything with three or more steps or an architectural decision, the agent enters plan mode first. If something goes sideways it stops and replans instead of pushing on. Research and parallel analysis get handed to subagents so the main context stays clean.

Every correction you make gets written to tasks/lessons.md as a rule the agent follows next time. The plan itself lives in tasks/todo.md with checkable items, and a review section is appended when the work is done. One rule is blunt: never mark a task complete without showing it works — tests, logs, a diff of behaviour before and after.

The elegance rule applies to non-trivial changes only; for simple obvious fixes the skill tells the agent to skip it rather than over-engineer. Bug reports are handled without hand-holding: read the logs and failing tests, fix the root cause. If your project has no tasks directory yet, you will need one, because the skill writes into it as it goes.