new-product

To design system architecture for a new product, you can input a natural language description or documentation paths to trigger a multi-stage research workflow. This process analyzes runtime, abstraction, integration, and rendering layers to produce detailed architecture documentation and an implementation plan.

Documenting technology stack trade-offs is handled by generating an executive ARCHITECTURE-SUMMARY.md alongside detailed files like runtime-execution.md and abstraction-layer.md. These artifacts capture web-wide analysis of patterns and provide a ready-to-review implementation plan for stakeholder alignment.

Yes, you can use a natural language product description to generate technical architecture documentation. The research workflow accepts natural language input, asks targeted clarifying questions to tailor decisions, and outputs structured files covering runtime execution, integration layers, and output rendering.

Yes, the architecture research process supports iterative clarification for deployment and scale goals. It asks targeted questions during the workflow to align the generated technology stack and system architecture with your specific operational requirements and product objectives.

Automating architecture research for a new product idea generates an ARCHITECTURE-SUMMARY.md for stakeholder review, alongside big-idea.md, runtime-execution.md, abstraction-layer.md, integration-layer.md, and output-rendering.md. These artifacts provide comprehensive documentation of the evaluated stack and system design.