Software & DevOpsDone with Claude Code Sep 6, 2026
Take ideas to implementation with a planning-command pipeline
A solo SaaS founder uses a custom five-command agent flow (intent, impact analysis, planning, execution, review) with lint guardrails to ship features in a production product.
- What They Did
- The founder built five chained commands (intent, impact analysis, iterative planning, execution orchestration, review/demo) that all update one plan file in git, which he reviews at each stage. A shared CONTRIBUTING.md guides agents, ESLint rules run as post-edit hooks, and a Bash-approval script screens commands. When the agent misbehaves, it writes a new rule with tests.
- How It Went
- An orchestrator script turning plans into workflows cut token spend to about 20% and runtime from 5-6 hours to 20-30 minutes. He still reviews most code via git diff, and calls it mostly clean.
- Worth Knowing
- The guardrails grew incrementally: each unwanted agent action or approval prompt became a new lint rule or approval rule, so expect to keep investing in them.
Try it yourself with Claude Code
Set up a planning pipeline for my project in [repo or product name] as custom slash commands: one to capture intent, one for impact analysis, one for planning, one for execution, and one for review. Make the execution step run [my lint and test commands] and stop if they fail. Test it on this small feature: [feature idea]. Stop when the feature has gone through all five steps and I have a reviewed diff, and do not commit or push without asking me.