brainstorming

To brainstorm feature design, use a structured workflow to explore user intent and design options for new features. This process discovers requirements and approved designs before committing to implementation planning, ensuring you formalize specs correctly.

The devflow pipeline approach for spec handoff ensures brainstorming terminates by returning control at the correct stage. This prevents jumping ahead to writing plans directly, requiring you to formalize specifications before proceeding to implementation.

To start exploring feature behavior changes, invoke the canonical devflow entry point with your feature goal and known constraints. This delegates inputs to the upstream brainstorming workflow while preserving your original parameters for design discovery.

You cannot skip brainstorming to jump directly to writing plans. The workflow blocks direct transition to writing plans and instead returns control for the spec formalization step, ensuring requirements and intent are discovered first.

The brainstorming workflow does not require direct invocation of upstream MCP skills. It provides a single canonical entry point that delegates inputs automatically, so callers never need to know or directly invoke the upstream skill themselves.