build-from-design

To generate code from design documents, you can trigger an orchestrated pipeline using commands like '/build' or 'implement the design'. The workflow decomposes work into modules, then sequentially runs implementer, test-writer, and reviewer agents to produce the codebase.

An automated software development pipeline translates specifications into functional code sequentially. It decomposes work into manageable modules and utilizes specialized agents for planning, implementation, testing, and review to ensure dependencies are handled correctly.

Yes, you can generate tests and review reports alongside your codebase from a spec. The pipeline utilizes distinct test-writer and reviewer agents sequentially after implementation to produce comprehensive tests and a review report.

To start building a new feature from a markdown design file, trigger the workflow by instructing it to implement the design found in './my-design.md' based on the specification in './my-spec.md', which kicks off the automated pipeline.

Yes, the design to code pipeline handles module dependencies automatically. It decomposes the overall work into manageable modules during the planning phase, ensuring that all dependencies are correctly structured before implementation begins.

Automating code generation from specs requires clear specification and design documents to function effectively. Without well-defined input documents for the sequential agents to process, the generated codebase, tests, and review reports may lack accuracy.