harness-builder

You can automate code generation by reading spec.md and contract.md, then writing actual HTML, CSS, JS, or TS source files that satisfy the requirements. The process installs dependencies, verifies the build, and commits changes automatically.

To fix QA feedback issues, process feedback.md when present and apply iterative refinement strategies to update the current implementation. This ensures the generated source code meets acceptance criteria before committing.

Spec-driven code generation handles iterative refinement by using a REFINE strategy to improve the current implementation or a PIVOT strategy to rewrite when necessary, ensuring code meets QA feedback and acceptance criteria.

Yes, you can generate React and Vite production-ready source files directly from product specs. The workflow creates actual code files, installs required dependencies, verifies the build, and commits the changes.

No, you do not need to manually install dependencies. The code generation workflow automatically installs dependencies, verifies the build succeeds, and commits changes after writing the actual source files.

You should use a PIVOT strategy to rewrite the implementation when current code cannot meet QA feedback, and use REFINE to incrementally improve existing source files to satisfy acceptance criteria.