brainstorming

Clarifying complex requirements involves asking questions one at a time and proposing 2-3 approaches with trade-offs. This skill generates a committed design specification document and gates implementation until you explicitly approve the spec.

Writing a design spec for multi-component architecture decisions requires decomposing cross-cutting concerns and analyzing trade-offs. This skill explores your project context, proposes visual mockups, and commits the validated spec to your docs directory.

The best way to compare design approaches is by generating 2-3 options with explicit trade-offs and a recommended option. This skill provides a browser-based visual companion for side-by-side comparisons and mockups during the brainstorming process.

Yes, you can use visual mockups and diagrams when clarifying cross-cutting concerns. The skill offers a browser-based visual companion that provides side-by-side comparisons and mockups when visual questions are anticipated.

Yes, this spec-writing process enforces a hard gate that blocks implementation. It performs a spec self-review and does not invoke implementation actions until the user explicitly approves the validated design specification.