mcpField
F
fstack-build

fstack-build

github.com/flaviocopesAgent workflows3162 installsUpdated 15w ago
Repository

About fstack-build

fstack-build is a coding-agent skill for carrying out an approved PLAN.md in small, verified steps. It pauses for decisions or unplanned work instead of making changes without approval.

Key features

  1. 01Implements the next unfinished plan step
  2. 02Verifies each change before continuing
  3. 03Reports progress and marks steps complete
  4. 04Pauses for decisions or plan changes

Use cases

  1. 01Building a feature from an approved PLAN.md
  2. 02Verifying changes one planned step at a time
  3. 03Requesting approval for choices that affect later work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/flaviocopes/fstack --skill fstack-build

After installing, type/fstack-buildin Claude Code to confirm it loaded.

Details

From the project README

/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.md exists and the user says to build.
  • /fstack routed here because the plan is approved and ready.

Steps

  1. Take the first unfinished step from PLAN.md.
  2. Implement it with the smallest change that works.
  3. Verify it. Run it, run the test, load the page — whatever fits.
  4. Report in 2–3 sentences: what changed, how you verified it.
  5. Mark the step done in PLAN.md.
  6. If the next step involves a real choice — library, API shape, naming that leaks into the public surface — stop and ask before proceeding.
  7. 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)

Comments

Markdown supported