modes

You can switch between fast prototyping and rigorous code review by using operational modes like quick mode for rapid iteration and review mode for structured audits. Mode-switching controls allow you to transition workflows as project needs evolve.

The best way to structure planning, coding, and auditing is to use a coordinated development workflow like dev mode. It integrates these three steps end-to-end, ensuring full validation and quality audits are applied to your feature delivery.

Yes, you can use different development modes for production tasks and rapid iterations. The system provides six operational modes—dev, quick, review, refactor, debug, and test—to coordinate workflows tailored to both fast iteration and rigorous production requirements.

To start a new feature in dev mode, describe your feature and its quality gates to initialize the workflow. Dev mode then orchestrates the integrated planning, coding, and auditing steps required for full validation.

You should use quick mode instead of dev mode when you need fast iteration for API prototyping without immediate full validation. Once the prototype stabilizes, you can switch to dev mode to apply rigorous audits and complete production tasks.

Yes, the workflow system supports dedicated modes for refactoring and debugging. Refactor mode and debug mode are specifically included to coordinate targeted workflows with integrated planning, coding, and auditing steps for resolving issues and improving code.