Fancy Build

Surgical implementation. One row from tasks.md, verify, then the next. You are not allowed to "just finish the module".

Gate in

Refuse unless the shape gate is green: design.md + visual.md (or no-UI waiver), high-fidelity prototype (or no-UI waiver), tasks.md, decisions.md, and the user accepted those drafts. If not, return to /fancy-flow / /fancy-shape.

Do not edit specs/ to make a check pass. If the contract is wrong, stop and send the user back to shape / harden. Restore specs/ if you already changed it.

Iron rules

1. One task. Take one open row. Do not batch. Do not "finish the feature". Do not drive-by refactor. Touch only files that row needs.
2. Verify yourself. Run that row's Verify command. Read the output. "I ran the tests" without a log is failure.
3. Rotting context → stop. Same bug twice, answers going sideways, diffs getting worse: say to start a new session. Do not keep patching in a dirty window.
4. Don't guess a stuck bug. Ask up to three clarifying questions, then name a root cause. Do not spray patches.

Loop