super-brainstorm

To turn vague feature ideas into validated design specs, run a structured plan-mode interview that scans your codebase and docs to resolve requirements, then outputs an approved specification to your repository plans path.

The best way to plan architectural decisions safely is by enforcing spec-first hard gates that block code changes and scaffolding until a multi-branch requirements discovery interview is fully approved.

A codebase-first design interview works by performing deep reconnaissance on existing documentation and source code, then conducting a relentless linear question flow to resolve constraints before writing a design spec.

Yes, you can write implementation-ready specifications directly to the docs/plans directory after completing an internal review loop to catch gaps before proceeding with the feature design.

Yes, this approach supports multi-branch requirements discovery by applying structured questioning to component design and system changes, ensuring all architectural constraints are resolved before spec approval.

You should use a spec-first workflow to prevent costly rework, because it converts architectural uncertainty and vague requests into an approved design specification before any implementation work begins.