brainstorming

Enforce structured design exploration and stakeholder approval before implementation.

3|Updated Apr 21, 2024
One-click install
npx skills add https://github.com/gabrielfruet/.dotfiles --skill brainstorming-gabrielfruet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/gabrielfruet/.dotfiles/tree/main/pi/agent/skills/brainstorming
Command: npx skills add https://github.com/gabrielfruet/.dotfiles --skill brainstorming-gabrielfruet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jumping straight into coding without clear design leads to rework, missed requirements, and wasted effort on features that don't align with user needs or project goals.

Core Features & Use Cases

  • Structured Design Process: Guides you through context exploration, requirement clarification, and trade-off analysis for any creative or technical project.
  • Approval Gate: Enforces signoff on the final design before any implementation work begins to eliminate costly rework.
  • Use Case: When building a new user notification system, use this skill to first evaluate push vs in-app notification tradeoffs, align on requirements with stakeholders, and get approval on the design before writing any code.

Quick Start

Use the brainstorming skill to design the new user profile editing feature before starting any implementation work.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I enforce structured software design before coding to eliminate rework?

Structured software design prevents rework by enforcing requirement clarification, trade-off analysis, and design documentation prior to coding, ensuring final design signoff is secured before implementation starts.

What is the best way to evaluate feature trade-offs during requirement planning?

Evaluating feature trade-offs requires structured design exploration to compare implementation options and align technical decisions with stakeholder requirements before development begins.

Can I use an approval workflow for design documentation in feature development?

Yes, an approval workflow enforces stakeholder signoff on design documentation, ensuring requirement clarification and trade-off analysis are completed before implementation begins.

Does this structured design process work for component design and new functionality planning?

Yes, structured design exploration applies to component design and new functionality planning, enforcing requirement clarification and trade-off analysis across all creative and technical software engineering projects.

When do I need requirement clarification for a new user notification system?

You need requirement clarification for a new user notification system before coding to evaluate push versus in-app notification tradeoffs and align on requirements with stakeholders.