Move features from idea to shipped code through a staged plan file
Idea + starter prompt, not run by us yet
For: Solo founders shipping features in a live product with an agent
A solo SaaS founder chains five commands: intent, impact check, planning, running the work and review. Each one updates a single plan file in git, which he checks at every stage. A shared CONTRIBUTING.md guides the agent, lint rules run after edits and a script screens shell commands. When the agent misbehaves, it adds a new tested rule. A later orchestrator script cut tokens and run time a lot.
Steps
- Write a shared guide for how code in your project should look.
- Create commands for each stage, all writing to one plan file kept in git.
- Review the plan file at each stage before moving on.
- Add lint rules or approval rules whenever the agent does something unwanted.
- Keep reading the git diff before merging, since guardrails need ongoing work.
Starter prompt
I want to build [feature] in [project]. Step 1: write down the intent in [plan file]. Step 2: list every part of the code this will affect and the risks. Step 3: write a step by step plan. Stop after each step so I can review the plan file. Do not write code until I approve the plan. When you build, work on a new branch, run lint and tests, and show me the diff. Do not merge.
Original post: Hacker News · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.