wz:brainstorming

Convert operator briefs into approved designs with documented trade-offs.

3|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-brainstorming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wz:brainstorming
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/brainstorming
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill wz-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming session design helps convert operator briefs into an approved design with explicit trade-offs, ensuring no steps are skipped.

Core Features & Use Cases

  • Follows a canonical command matrix to structure task exploration
  • Guides multi-step design with trade-off documentation and guardrails
  • Provides a plan for design-review and writing plans after approval

Quick Start

To start brainstorming for a new task, instruct the agent to review the operator brief and follow the canonical routing matrix before drafting design options.

Frequently Asked Questions about wz:brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn an operator brief into an approved design with trade-offs?

To turn an operator brief into an approved design, review the brief and follow a canonical routing matrix to draft design options. This process enforces explicit trade-off documentation and risk assessment before proceeding.

What is the best way to structure design exploration and decision logging for engineering workflows?

Structuring design exploration requires following a canonical command matrix to guide multi-step design tasks. It enforces repeatable guardrails by requiring explicit decision logging and acceptance criteria before moving forward.

How do I document design trade-offs and perform risk analysis during product planning?

Documenting design trade-offs during product planning involves outlining roles, steps, and risks using structured guidance. The process requires explicit trade-off documentation and risk assessment to ensure no steps are skipped.

Does this brainstorming workflow require explicit acceptance criteria before proceeding?

Yes, this brainstorming workflow requires explicit acceptance criteria before proceeding to design review. Enforcing these acceptance criteria ensures a repeatable process for converting briefs into approved designs.

Can I use this design workflow for both product design and engineering tasks?

Yes, you can use this design workflow for both product design and engineering tasks. It applies across both workflows by providing structured guidance for task exploration, decision logging, and risk assessment.

When should I not use a canonical routing matrix for design exploration?

You should not use a canonical routing matrix for design exploration if your task lacks a clear operator brief or explicit acceptance criteria. The process requires these inputs to enforce repeatable guardrails and prevent skipped steps.