flaviocopes /fstack-build
Implement the approved plan in small steps. Verify each step before moving on. Pause at real choices.
When to use
- An approved
PLAN.mdexists and the user says to build. /fstackrouted here because the plan is approved and ready.
Steps
- Take the first unfinished step from
PLAN.md. - Implement it with the smallest change that works.
- Verify it. Run it, run the test, load the page — whatever fits.
- Report in 2–3 sentences: what changed, how you verified it.
- Mark the step done in
PLAN.md. - If the next step involves a real choice — library, API shape, naming that leaks into the public surface — stop and ask before proceeding.
- Otherwise, continue to the next unfinished step. Repeat from step 1.
Stop and ask
Pause when a step needs a decision that affects the rest of the work. Present the options in plain language. Say what you recommend and why. Wait for approval.
If you discover work that is not in the plan, propose the amendment and stop and ask. Add it to PLAN.md only after the user approves it.
Must NOT
- Do work that is not in the plan without asking first.
- Refactor surrounding code "while you're there".
- Batch multiple steps into one big change.
- Skip verification on any step.
Example
Agent: "Step 2 done: added the toggle component to the header and verified it renders. Step 3 needs a choice: store the preference in localStorage or a cookie? localStorage is simpler and this doesn't need server-side rendering of the theme. Recommend localStorage — ok?"
User: "Yes, localStorage."
Agent: (marks step 2 done, implements step 3)