Five commands and a plan file in git

What was done

On 06 September 2026 gojkoa writes that he works for himself on a SaaS product that has been in production for 7 years and is used by customers. He calls it decently profitable. The flow has 5 commands: intent, impact analysis, planning, execution, and review with a demo. They build one plan file in git that he reads as it goes. CLAUDE.md loads CONTRIBUTING.md. Eslint runs as a hook after edit and write. Custom rules have grown to thousands. When they catch the agent in a habit it should not have, it writes a new rule with tests. A regulator script is a hook in front of Bash: it parses the command and approves, rejects, or asks. An orchestrator turns the plan file into Claude Dynamic Workflows. Token spend is now about ~20% of earlier workflows. Time went from an average of 5-6 hours per workflow to about 20-30 minutes. The 10-15 minute wait while Claude built the workflow is gone. A demo command records webm with Playwright. He still reads most diffs when the code is done.

How it went

He feels productive. Token spend is about ~20% of earlier workflows, and the time is about 20-30 minutes against an average of 5-6 hours. He does not say everything is published.

Worth knowing

Profitability has no figure. Thousands of rules is not an exact count. The about ~20% is an estimate. He still reads most diffs.

How to do it

1. Write the intent for [task] in the plan file and read it before coding.
2. Let the hooks and tests answer before you look at the diff.
3. Read the diff yourself. Do not deploy before you are done with it.