architect-flow

To plan feature architecture for SpawnForge, apply a spec-first workflow that produces a markdown spec in the specs/ directory, a JSON event schema, required Bevy systems, and a React components outline before coding begins.

A spec-first workflow for multi-system design evaluates a feature concept to draft formal specs, yielding a markdown design document, a defined JSON event schema, and outlined Bevy gameplay systems alongside React frontend components.

To generate a JSON event schema for Bevy systems and React components, execute an analysis-driven planning protocol that defines multi-system design decisions and outputs the schema alongside a markdown spec and component outlines.

You can use this planning workflow for React and Bevy integration projects within the SpawnForge context, specifically when designing multi-system changes or answering formal feature planning queries before development starts.

The best way to document design decisions for SpawnForge features is generating a specs/ markdown file through an analysis-driven protocol, ensuring naming conventions and architectural choices are formally recorded prior to implementation.

You should not use a spec-first architecture workflow for rapid prototyping or minor adjustments where formal specs, JSON event schemas, and multi-system Bevy and React outlines are unnecessary overhead before coding.